2 |
Approval of the agenda |
|
R4-2207600 |
RAN4#102-e Meeting Report |
ETSI MCC |
R4-2207601 |
Agenda for RAN4#103-e |
RAN4 Chair (Huawei) |
R4-2207602 |
RAN4#103-e E-Meeting Arrangements and Guidelines |
RAN4 Chair (Huawei) |
R4-2211347 |
RAN4#103-e BS_Demod_Testing Session meeting minutes |
RAN4 vice chair (Samsung) |
3 |
Letters / reports from other groups / meeting |
|
R4-2207603 |
LS on updated Rel-17 LTE and NR higher-layers parameter list |
RAN1 |
R4-2207604 |
LS on updated Rel-16 RAN1 UE features lists for NR after RAN1#108-e |
RAN1 |
R4-2207605 |
LS on the dropping rule of DL signals/channels for capability 1B and 2 |
RAN1 |
R4-2207606 |
LS on use of CQI table for NB-IoT DL 16QAM |
RAN1 |
R4-2207607 |
LS on operation with and without SSB for RedCap UE |
RAN1 |
R4-2207608 |
LS on UE capability for 16QAM for NB-IoT |
RAN1 |
R4-2207609 |
LS on updated Rel-17 RAN1 UE features list for LTE |
RAN1 |
R4-2207610 |
LS on updated Rel-17 RAN1 UE features list for NR |
RAN1 |
R4-2207611 |
LS on upper layers parameters for Rel-17 eIAB |
RAN1 |
R4-2207612 |
Reply LS to RAN4 on RRM relaxation |
RAN2 |
R4-2207613 |
Reply LS on Signalling of PC2 V2X intra-band concurrent operation |
RAN2 |
R4-2207614 |
LS on TCI state indication |
RAN2 |
R4-2207615 |
Reply LS on interruption for PUCCH SCell activation in invalid TA case |
RAN2 |
R4-2207616 |
LS on coordination of R17 gap features |
RAN2 |
R4-2207617 |
LS on BWP operation without bandwidth restriction |
RAN2 |
R4-2207618 |
LS on measurement gaps enhancements for NTN |
RAN2 |
R4-2207619 |
LS on introduction of an offset to transmit CD-SSB and NCD-SSB at different times |
RAN2 |
R4-2207620 |
Reply LS to RAN4 on RLM/BFD relaxation for ePowSav |
RAN2 |
R4-2207621 |
LS on TA validation for CG-SDT |
RAN2 |
R4-2207622 |
Questions concerning the implementation of RAN1 agreements in NRPPa |
RAN3 |
R4-2207623 |
LS on lower humidity limit in normal temperature test environment |
RAN5 |
R4-2207624 |
LS on Additional RF requirements for NS_03U, NS_05U and NS_43U |
RAN5 |
R4-2207625 |
LS on SCell Dropping in FR2 RF UL-CA tests |
RAN5 |
R4-2207626 |
LS to ISED-Canada to clarify the RSS-195 requirement related to wireless communication service equipment operating in 2305-2320 MHz / 2345-2360 MHz frequency range |
RAN |
R4-2207627 |
LS on presentation of EUWENA and involvement in 3GPP on Non Public Network |
EUWENA |
R4-2207628 |
FREQUENCY ARRANGEMENTS FOR IMT IN THE BAND 470 – 703 MHZ |
APT Wireless Group |
R4-2207713 |
Reply to Liaison statement of 3GPP TSG RAN on the inclusion of the 6425-7125 MHz frequency band in the 3GPP specification for 5G-NR / IMT-2020 systems |
RCC Commission on Spectrum and Satellite Orbits |
R4-2210236 |
Request information on progress and timeline relating to 6 GHz NR licensed bands |
GSMA |
R4-2210237 |
LS on Rel-18 WI related to vehicular distributed antenna systems |
5GAA WG4 |
R4-2210349 |
LS on CTIA Certification OTA Performance Test Plan Version 4.0 Publication |
CTIA Certification OTA Working Group |
R4-2210431 |
LS to 3GPP RAN WG4 on the interferer signal definition for the RMR900 BS Rx blocking requirement |
ETSI TC RT |
R4-2210432 |
LS on eIAB MAC CEs |
RAN2 |
R4-2211136 |
Reply LS on eIAB MAC CEs |
RAN1 |
R4-2211137 |
LS on updated Rel-17 RAN1 UE features list for LTE |
RAN1 |
R4-2211138 |
LS on updated Rel-17 RAN1 UE features list for NR |
RAN1 |
R4-2211177 |
Reply LS on lower Rx beam sweeping factor for latency improvement |
RAN1 |
R4-2211178 |
Reply LS on applicable number of PFL for the gapless PRS measurement |
RAN1 |
R4-2211198 |
LS reply on clarification of dualPA-Architecture capability |
RAN2 |
R4-2211199 |
Reply LS on operation with and without SSB for RedCap UE |
RAN2 |
4.1 |
NR WIs |
|
R4-2211165 |
Draft CR on TS 36.171 requirements for support of A-GNSS |
CATT, CAICT, CENC |
R4-2211166 |
Draft CR on TS 38.171 requirements for support of A-GNSS |
CATT, CAICT, CENC |
R4-2211244 |
CR on TS 36.171 requirements for support of A-GNSS |
MCC, CATT |
R4-2211245 |
CR on TS 37.171 requirements for support of A-GNSS |
MCC, CATT |
R4-2211246 |
CR on TS 38.171 requirements for support of A-GNSS |
MCC, CATT |
R4-2211247 |
CR on TS 38.171 requirements for support of A-GNSS |
MCC, CATT |
R4-2211333 |
CR on TS 36.171 requirements for support of A-GNSS |
MCC, CATT |
4.1.1.1 |
FR1 (38.101-1) |
|
R4-2207827 |
Draft CR for 38.101-1: Incorrect reference of R2 IE in UL Tx Switching (R17) |
SoftBank Corp. |
R4-2207866 |
draft CR: Update of UE capability name for Tx switching |
China Telecom |
R4-2207886 |
CR for 38.101-1-gb0: Correction for n7 A-MPR (NS_46) |
Keysight Technologies UK Ltd, Qualcomm Inc. |
R4-2207887 |
CR for 38.101-1-h50: Correction for n7 A-MPR (NS_46) |
Keysight Technologies UK Ltd, Qualcomm Inc. |
R4-2207996 |
CR for 38.101-1 Rel16 Correction for n65 15, 20MHz Coexistence |
Qualcomm Incorporated |
R4-2207997 |
CR for 38.101-1 Rel17 Correction for n65 15, 20MHz Coexistence |
Qualcomm Incorporated |
R4-2207998 |
CR for 38.101-1 Rel16 Minor AMPR Corrections for n65 to account for SCS |
Qualcomm Incorporated |
R4-2207999 |
CR for 38.101-1 Rel17 Minor AMPR Corrections for n65 to account for SCS |
Qualcomm Incorporated |
R4-2208001 |
n65 AMPR and Coexistence revisited |
Qualcomm Incorporated |
R4-2208401 |
Discussion on 30MHz reconfiguration failure when accessing 40MHz network of n28 |
CMCC |
R4-2208579 |
Update of UL MIMO transmit quality definitions |
Rohde & Schwarz |
R4-2208580 |
Update of UL MIMO transmit quality definitions |
Rohde & Schwarz |
R4-2208581 |
Update of UL MIMO transmit quality definitions |
Rohde & Schwarz |
R4-2208596 |
Miscelleous corrections on A-MPR requirements for Intra-band CA |
vivo |
R4-2208597 |
Miscelleous corrections on A-MPR requirements for Intra-band CA |
vivo |
R4-2208664 |
draft CR to TS38.101-1[R15] Some Corrections for Transmitter characteristics |
ZTE Corporation |
R4-2208665 |
draft CR to TS38.101-1[R16] Some Corrections for Transmitter and Receiver characteristics |
ZTE Corporation |
R4-2208686 |
Draft CR to 38.101-1: Correction on terms for NR DC Pcmax |
ZTE Corporation |
R4-2208687 |
Draft CR to 38.101-1: Correction on terms for NR DC Pcmax |
ZTE Corporation |
R4-2208693 |
Draft CR to 38.101-1: Correction on MSD value for DC_1A-8A_n78A |
ZTE Corporation, CHTTL |
R4-2208694 |
Draft CR to 38.101-1: Correction on MSD value for DC_1A-8A_n78A and DC_1A_n8A-n78A |
ZTE Corporation, CHTTL |
R4-2208695 |
Draft CR to 38.101-1: Correction on MSD value for DC_1A-8A_n78A and DC_1A_n8A-n78A |
ZTE Corporation, CHTTL |
R4-2208738 |
Correction to Pcmax: application of p-NR-FR1 for one CG with one uplink serving cell |
Ericsson |
R4-2208739 |
Correction to Pcmax: application of p-NR-FR1 for one CG with one uplink serving cell |
Ericsson |
R4-2208740 |
Correction to Pcmax: application of p-NR-FR1 for one CG with one uplink serving cell |
Ericsson |
R4-2208741 |
Correct the NS value applicability for operation in the n77 frequency range in the US |
Ericsson |
R4-2208742 |
Correct the NS value applicability for operation in the n77 frequency range in the US |
Ericsson |
R4-2209022 |
Draft CR for TS 38.101-1 Section 6.2.2 |
ZTE Wistron Telecom AB |
R4-2209023 |
Draft CR for TS 38.101-1 Section 6.2.2 |
ZTE Wistron Telecom AB |
R4-2209024 |
Draft CR for TS 38.101-1 Section 6.2.2 |
ZTE Wistron Telecom AB |
R4-2209025 |
Draft CR for TS 38.101-2 Section 6.2.2 |
ZTE Wistron Telecom AB |
R4-2209026 |
Draft CR for TS 38.101-2 Section 6.2.2 |
ZTE Wistron Telecom AB |
R4-2209027 |
Draft CR for TS 38.101-2 Section 6.2.2 |
ZTE Wistron Telecom AB |
R4-2209092 |
Draft CR to 38.101-1 R16 adding the missing additional spurious emission requirement for CA_NC_NS_04 |
Xiaomi |
R4-2209093 |
Draft CR to 38.101-1 R17 adding the missing additional spurious emission requirement for CA_NC_NS_04 |
Xiaomi |
R4-2209149 |
FR1 UL coherent MIMO |
Anritsu Limited |
R4-2209150 |
Draft CR to add ‘Annex G Difference of relative phase and power errors’ for FR1 UL coherent MIMO |
Anritsu Limited |
R4-2209151 |
Draft CR to add ‘Annex G Difference of relative phase and power errors’ for FR1 UL coherent MIMO |
Anritsu Limited |
R4-2209152 |
Draft CR to add ‘Annex G Difference of relative phase and power errors’ for FR1 UL coherent MIMO |
Anritsu Limited |
R4-2209160 |
Draft CR to modify MPR and AMPR definitions for almost contiguous allocations |
Anritsu Limited |
R4-2209161 |
Draft CR to modify MPR and AMPR definitions for almost contiguous allocations |
Anritsu Limited |
R4-2209162 |
Draft CR to modify MPR and AMPR definitions for almost contiguous allocations |
Anritsu Limited |
R4-2209310 |
draftCR for TS 38.101-1 Rel-15: Corrections on Single Bands Coex |
Apple |
R4-2209311 |
draftCR for TS 38.101-1 Rel-16: Corrections on Single Bands Coex |
Apple |
R4-2209312 |
draftCR for TS 38.101-1 Rel-17: Corrections on Single Bands Coex |
Apple |
R4-2209313 |
draftCR for TS 36.101 Rel-15: Corrections on Single Bands Coex |
Apple |
R4-2209314 |
draftCR for TS 36.101 Rel-16: Corrections on Single Bands Coex |
Apple |
R4-2209315 |
draftCR for TS 36.101 Rel-17: Corrections on Single Bands Coex |
Apple |
R4-2209324 |
Draft CR for TS 36.101: P-Max definition correction for bands other than Band 41 |
Apple |
R4-2209325 |
Draft CR for TS 36.101: P-Max definition correction for bands other than Band 41 |
Apple |
R4-2209326 |
Draft CR for TS 36.101: P-Max definition correction for bands other than Band 41 |
Apple |
R4-2209334 |
Draft CR for 38.101-1 to add note 5 for band n83(R15) |
Huawei, HiSilicon |
R4-2209335 |
Draft CR for 38.101-1 to add note 5 for band n83(R16) |
Huawei, HiSilicon |
R4-2209336 |
Draft CR for 38.101-1 to add note 5 for band n83(R17) |
Huawei, HiSilicon |
R4-2209337 |
Draft CR for 38.101-1 to clarify the restriction of band n28 for CA_n20-n28(R16) |
Huawei, HiSilicon |
R4-2209338 |
Draft CR for 38.101-1 to clarify the restriction of band n28 for CA_n20-n28(R17) |
Huawei, HiSilicon |
R4-2209342 |
Draft CR for 38.101-1 to add the missing simultaneous Rx/Tx capability for SUL band combinations (R16) |
Huawei, HiSilicon |
R4-2209343 |
Draft CR for 38.101-1 to add the missing simultaneous Rx/Tx capability for SUL band combinations (R17) |
Huawei, HiSilicon |
R4-2209344 |
Draft CR for 38.101-1 to mainteinance NR V2X UE spec (R16) |
Huawei, HiSilicon |
R4-2209345 |
Draft CR for 38.101-1 to mainteinance NR V2X UE spec (R17) |
Huawei, HiSilicon |
R4-2209350 |
Draft CR for 38.101-1 to add exception clause for inter-band CA REFSENS (R16) |
Huawei, HiSilicon |
R4-2209351 |
Draft CR for 38.101-1 to add exception clause for inter-band CA REFSENS (R17) |
Huawei, HiSilicon |
R4-2209380 |
Draft CR on clarification of Tx DC location in FR1 CA (R16) |
OPPO |
R4-2209381 |
Draft CR on clarification of Tx DC location in FR1 CA (R17 CAT-A) |
OPPO |
R4-2209752 |
draft CR for TS 38.101-1: correction for DC location reporting (R16 cat-F) |
Huawei, HiSilicon |
R4-2209753 |
draft CR for TS 38.101-1: correction for DC location reporting (R17 cat-A) |
Huawei, HiSilicon |
R4-2209782 |
A draft CR to clarify the 100 kHz channel raster applicability |
Nokia, Nokia Shanghai Bell |
R4-2209783 |
A draft CR to clarify the 100 kHz channel raster applicability |
Nokia, Nokia Shanghai Bell |
R4-2209784 |
A draft CR to clarify the 100 kHz channel raster applicability |
Nokia, Nokia Shanghai Bell |
R4-2210109 |
CR to TS 38.101-3 V16.11.0 on intra-band ULCA UL configurations |
Skyworks Solutions Inc. |
R4-2210201 |
Correction to out-of-band blocking ranges |
Qualcomm Incorporated |
R4-2210202 |
Correction to out-of-band blocking ranges |
Qualcomm Incorporated |
R4-2210203 |
Correction to out-of-band blocking ranges |
Qualcomm Incorporated |
R4-2210238 |
Email discussion summary for [103-e][101] R15_R16_Maintenance |
Moderator (OPPO) |
R4-2210346 |
Draft CR to modify MPR and AMPR definitions for almost contiguous allocations |
Anritsu Limited |
R4-2210347 |
Draft CR to modify MPR and AMPR definitions for almost contiguous allocations |
Anritsu Limited |
R4-2210348 |
Draft CR to modify MPR and AMPR definitions for almost contiguous allocations |
Anritsu Limited |
R4-2210438 |
Email discussion summary for [103-e][101] R15_R16_Maintenance |
Moderator (OPPO) |
R4-2210540 |
WF on 30MHz reconfiguration failure when accessing 40MHz network of n28 |
CMCC |
R4-2210541 |
WF on FR1 UL coherent MIMO test |
Anritsu |
R4-2210542 |
WF on EIRP-based test metric for FR2 SEM |
Apple |
R4-2210543 |
WF on intrabandENDC-Support |
Xiaomi |
R4-2210682 |
Draft CR to add ‘Annex G Difference of relative phase and power errors’ for FR1 UL coherent MIMO |
Anritsu Limited |
R4-2210683 |
draftCR for TS 38.101-1 Rel-15: Corrections on Single Bands Coex |
Apple |
R4-2210684 |
CR for 38.101-1 Rel16 Correction for n65 15, 20MHz Coexistence |
Qualcomm Incorporated |
R4-2210685 |
n65 AMPR and Coexistence revisited |
Qualcomm Incorporated |
R4-2210686 |
Correct the NS value applicability for operation in the n77 frequency range in the US |
Ericsson |
R4-2210687 |
Draft CR to 38.101-1 R16 adding the missing additional spurious emission requirement for CA_NC_NS_04 |
Xiaomi |
R4-2210688 |
Draft CR for 38.101-1 to clarify the restriction of band n28 for CA_n20-n28(R16) |
Huawei, HiSilicon |
R4-2210689 |
Draft CR for 38.101-1 to mainteinance NR V2X UE spec (R16) |
Huawei, HiSilicon |
R4-2210690 |
draftCR for TS 36.101 Rel-15: Corrections on Single Bands Coex |
Apple |
R4-2211162 |
draft CR for TS 38.101-1: correction for DC location reporting (R16 cat-F) |
Huawei, HiSilicon |
R4-2211182 |
Update of UL MIMO transmit quality definitions |
Rohde & Schwarz |
R4-2211251 |
Big CR for TS 38.101-1 Maintenance Part-1 (Rel-15) |
MCC, Vivo |
R4-2211252 |
Big CR for TS 38.101-1 Maintenance Part-1 (Rel-16) |
MCC, Vivo |
R4-2211253 |
Big CR for TS 38.101-1 Maintenance Part-1 (Rel-17) |
MCC, Vivo |
R4-2211262 |
Big CR for TS 36.101 Maintenance (Rel-14) |
Meta |
R4-2211263 |
Big CR for TS 36.101 Maintenance (Rel-15) |
Meta |
R4-2211264 |
Big CR for TS 36.101 Maintenance (Rel-16) |
Meta |
R4-2211265 |
Big CR for TS 36.101 Maintenance (Rel-17) |
Meta |
4.1.1.2 |
FR2 (38.101-2) |
|
R4-2207671 |
Draft CR for TS 38.101-2: Change FR2 ACLR verification test metric |
Apple |
R4-2207672 |
Draft CR for TS 38.101-2: Change FR2 ACLR verification test metric |
Apple |
R4-2207673 |
Draft CR for TS 38.101-2: Change FR2 ACLR verification test metric |
Apple |
R4-2207674 |
EIRP-based test metric for FR2 SEM verifications |
Apple |
R4-2207675 |
Draft CR for TS 38.101-2: Change FR2 SEM verification test metric |
Apple |
R4-2207676 |
Draft CR for TS 38.101-2: Change FR2 SEM verification test metric |
Apple |
R4-2207677 |
Draft CR for TS 38.101-2: Change FR2 SEM verification test metric |
Apple |
R4-2207786 |
Correction of FR2 UE configured transmitted power |
Apple |
R4-2207883 |
CR for 38.101-2-fh0: Correction for PC3 MPRnarrow |
Keysight Technologies UK Ltd, Skyworks Solutions Inc. |
R4-2207884 |
CR for 38.101-2-gb0: Correction for PC3 MPRnarrow |
Keysight Technologies UK Ltd, Skyworks Solutions Inc. |
R4-2207885 |
CR for 38.101-2-h50: Correction for PC3 MPRnarrow |
Keysight Technologies UK Ltd, Skyworks Solutions Inc. |
R4-2208611 |
draft CR to remove the LO exception of SEM in FR2 |
vivo |
R4-2208612 |
draft CR to remove the LO exception of SEM in FR2 |
vivo |
R4-2208634 |
Draft CR to TS 38.101-2 on corrections to RF requirement applicability(R15) |
vivo |
R4-2208635 |
Draft CR to TS 38.101-2 on corrections to RF requirement applicability(R16) |
vivo |
R4-2208636 |
Draft CR to TS 38.101-2 on corrections to RF requirement applicability(R17) |
vivo |
R4-2208871 |
Draft CR for clarification on Maximum input and ACS and IBB for FR2 DL intra and inter combinations for TS 38.101-2 |
NTT DOCOMO, INC |
R4-2208872 |
Draft CR for clarification on Maximum input and ACS and IBB for FR2 DL intra and inter combinations for TS 38.101-2 |
NTT DOCOMO, INC |
R4-2209378 |
Draft CR on clarification of PMPR in FR2 (R16) |
OPPO |
R4-2209379 |
Draft CR on clarification of PMPR in FR2 (R17 CAT-A) |
OPPO |
R4-2209383 |
Draft CR on clarification of Tx DC location in FR2 CA (R16) |
OPPO |
R4-2209402 |
Draft CR on clarification of Tx DC location in FR2 CA (R17 CAT-A) |
OPPO |
R4-2209626 |
Draft CR to TS 38.101-2 on UE multi-band relaxation factors for PC3 |
ZTE Corporation |
R4-2211192 |
Draft CR on clarification of PMPR in FR2 (R16) |
OPPO |
R4-2211254 |
Big CR for TS 38.101-2 Maintenance (Rel-15) |
MCC, Ericsson |
R4-2211255 |
Big CR for TS 38.101-2 Maintenance (Rel-16) |
MCC, Ericsson |
R4-2211256 |
Big CR for TS 38.101-2 Maintenance (Rel-17) |
MCC, Ericsson |
4.1.1.3 |
Requirements for 38.101-3 |
|
R4-2207824 |
Draft CR for 38.101-3: Missing definitions of PEMAX_NE-DC in Pcmax formulae (R15) |
SoftBank Corp. |
R4-2207825 |
Draft CR for 38.101-3: Missing definitions of PEMAX_NE-DC in Pcmax formulae (R16) |
SoftBank Corp. |
R4-2207826 |
Draft CR for 38.101-3: Missing definitions of PEMAX_NE-DC in Pcmax formulae (R17) |
SoftBank Corp. |
R4-2208782 |
Discussion on intra-band EN-DC combination |
Google Inc., Comcast, Federated Wireless, CableLabs |
R4-2208783 |
Draft CR for 38.101-3 Rel-16 intra-band contiguous EN-DC band combination |
Google Inc., Comcast, Federated Wireless, CableLabs |
R4-2208784 |
Draft CR for 38.101-3 Rel-17 intra-band contiguous EN-DC band combination |
Google Inc., Comcast, Federated Wireless, CableLabs |
R4-2208785 |
Draft CR for 38.101-3 Rel-16 intra-band non-contiguous EN-DC band combination |
Google Inc., Comcast, Federated Wireless, CableLabs |
R4-2208786 |
Draft CR for 38.101-3 Rel-17 intra-band non-contiguous EN-DC band combination |
Google Inc., Comcast, Federated Wireless, CableLabs |
R4-2208855 |
Discussion on intrabandENDC-Support |
Xiaomi |
R4-2208856 |
Draft CR for 38.101-3 Rel-16 to correct band combination for intra-band ENDC |
Xiaomi |
R4-2208857 |
Draft CR for 38.101-3 Rel-17 to correct band combination for intra-band ENDC |
Xiaomi |
R4-2208868 |
Draft CR for correction on missing band configuration in MSD table for IM |
NTT DOCOMO, INC |
R4-2208869 |
Draft CR for correction on missing band configuration in MSD table for IM |
NTT DOCOMO, INC |
R4-2208870 |
Draft CR for correction on missing band configuration in MSD table for IM |
NTT DOCOMO, INC |
R4-2209271 |
Draft CR on Pemax clarification in 38.101-3 (R15) |
OPPO |
R4-2209328 |
Draft CR on Pemax clarification in 38.101-3 (R16 CAT-A) |
OPPO |
R4-2209333 |
Draft CR on Pemax clarification in 38.101-3 (R17 CAT-A) |
OPPO |
R4-2209339 |
Draft CR for 38.101-3 to clarify the restriction of band n28 for DC_20_n28(R15) |
Huawei, HiSilicon |
R4-2209340 |
Draft CR for 38.101-3 to clarify the restriction of band n28 for DC_20_n28(R16) |
Huawei, HiSilicon |
R4-2209341 |
Draft CR for 38.101-3 to clarify the restriction of band n28 for DC_20_n28(R17) |
Huawei, HiSilicon |
R4-2209352 |
Draft CR for 38.101-3 to add DC_3C-7A-8A_n1A due to missing implementation (R16) |
Huawei, HiSilicon, DT |
R4-2209353 |
Draft CR for 38.101-3 to add DC_3C-7A-8A_n1A due to missing implementation (R17) |
Huawei, HiSilicon, DT |
R4-2209627 |
Draft CR to TS 38.307 on NR intra-band CA bandwidth class within FR1 (Rel-16) |
ZTE Corporation |
R4-2209628 |
Draft CR to TS 38.307 on NR intra-band CA bandwidth class within FR1 (Rel-17) |
ZTE Corporation |
R4-2209629 |
Draft CR to TS 38.307 on requirements for NR UE power class for FR1 (Rel-16) |
ZTE Corporation |
R4-2209630 |
Draft CR to TS 38.307 on requirements for NR UE power class for FR1 (Rel-17) |
ZTE Corporation |
R4-2209925 |
Correction of DC_3C_n7A-n78(2A) |
Nokia |
R4-2211257 |
Big CR for TS 38.101-3 Maintenance (Rel-15) |
MCC, Ericsson |
R4-2211258 |
Big CR for TS 38.101-3 Maintenance (Rel-16) |
MCC, Ericsson |
R4-2211259 |
Big CR for TS 38.101-3 Maintenance (Rel-17) |
MCC, Ericsson |
R4-2211260 |
Big CR for TS 38.307 Maintenance (Rel-16) |
MCC |
R4-2211261 |
Big CR for TS 38.307 Maintenance (Rel-17) |
MCC |
4.1.2 |
BS RF requirements |
|
R4-2208130 |
Draft CR for TS 38.104 R16: correction of some mistakes in the co-existence table |
CATT |
R4-2208131 |
Draft CR for TS 38.104 R17: correction of some mistakes in the co-existence table |
CATT |
R4-2210307 |
Email discussion summary for [103-e][301] BSRF_Maintenance |
Moderator (Ericsson) |
R4-2210504 |
Email discussion summary for [103-e][301] BSRF_Maintenance |
Moderator (Ericsson) |
R4-2210691 |
Draft CR for TS 38.104 R16: correction of some mistakes in the co-existence table |
CATT |
R4-2211281 |
Big CR for TS 36.124 Maintenance (Rel-8, CAT F) |
MCC, Nokia |
R4-2211282 |
Big CR for TS 36.124 Maintenance (Rel-9, CAT A) |
MCC, Nokia |
R4-2211283 |
Big CR for TS 36.124 Maintenance (Rel-10, CAT A) |
MCC, Nokia |
R4-2211284 |
Big CR for TS 36.124 Maintenance (Rel-11, CAT A) |
MCC, Nokia |
R4-2211285 |
Big CR for TS 36.124 Maintenance (Rel-12, CAT A) |
MCC, Nokia |
R4-2211286 |
Big CR for TS 36.124 Maintenance (Rel-13, CAT A) |
MCC, Nokia |
R4-2211287 |
Big CR for TS 36.124 Maintenance (Rel-14, CAT A) |
MCC, Nokia |
R4-2211288 |
Big CR for TS 36.124 Maintenance (Rel-15, CAT A) |
MCC, Nokia |
R4-2211289 |
Big CR for TS 36.124 Maintenance (Rel-16, CAT A) |
MCC, Nokia |
R4-2211290 |
Big CR for TS 36.124 Maintenance (Rel-17, CAT A) |
MCC, Nokia |
R4-2211291 |
Big CR for TS 37.105 Maintenance (Rel-15, CAT F) |
MCC, Huawei |
R4-2211292 |
Big CR for TS 37.105 Maintenance (Rel-16, CAT A) |
MCC, Huawei |
R4-2211293 |
Big CR for TS 37.105 Maintenance (Rel-17, CAT A) |
MCC, Huawei |
R4-2211294 |
Big CR for TS 37.141 Maintenance (Rel-15, CAT F) |
MCC, Ericsson |
R4-2211295 |
Big CR for TS 37.141 Maintenance (Rel-16, CAT F) |
MCC, Ericsson |
R4-2211296 |
Big CR for TS 37.141 Maintenance (Rel-17, CAT A) |
MCC, Ericsson |
R4-2211297 |
Big CR for TS 37.145-1 Maintenance (Rel-15, CAT F) |
MCC, Huawei |
R4-2211298 |
Big CR for TS 37.145-1 Maintenance (Rel-16, CAT F) |
MCC, Huawei |
R4-2211299 |
Big CR for TS 37.145-1 Maintenance (Rel-17, CAT A) |
MCC, Huawei |
R4-2211300 |
Big CR for TS 37.145-2 Maintenance (Rel-15, CAT F) |
MCC, Huawei |
R4-2211301 |
Big CR for TS 37.145-2 Maintenance (Rel-16, CAT F) |
MCC, Huawei |
R4-2211302 |
Big CR for TS 37.145-2 Maintenance (Rel-17, CAT A) |
MCC, Huawei |
R4-2211303 |
Big CR for TS 38.101-4 Maintenance (Rel-15, CAT F) |
MCC, Samsung |
R4-2211304 |
Big CR for TS 38.101-4 Maintenance (Rel-16, CAT F) |
MCC, Samsung |
R4-2211305 |
Big CR for TS 38.101-4 Maintenance (Rel-17, CAT A) |
MCC, Samsung |
R4-2211306 |
Big CR for TS 38.113 Maintenance (Rel-15, CAT F) |
MCC, ZTE |
R4-2211307 |
Big CR for TS 38.113 Maintenance (Rel-16, CAT A) |
MCC, ZTE |
R4-2211308 |
Big CR for TS 38.113 Maintenance (Rel-17, CAT A) |
MCC, ZTE |
R4-2211309 |
Big CR for TS 38.124 Maintenance (Rel-15, CAT F) |
MCC, ZTE |
R4-2211310 |
Big CR for TS 38.124 Maintenance (Rel-16, CAT A) |
MCC, ZTE |
R4-2211311 |
Big CR for TS 38.124 Maintenance (Rel-17, CAT A) |
MCC, ZTE |
R4-2211312 |
Big CR for TS 38.104 Maintenance RF part (Rel-15, CAT F) |
MCC, Ericsson |
R4-2211313 |
Big CR for TS 38.104 Maintenance RF part (Rel-16, CAT F) |
MCC, Ericsson |
R4-2211314 |
Big CR for TS 38.104 Maintenance RF part (Rel-17, CAT F) |
MCC, Ericsson |
R4-2211317 |
Big CR for TS 38.141-1 Maintenance RF part (Rel-16, CAT F) |
MCC, CATT |
R4-2211318 |
Big CR for TS 38.141-1 Maintenance RF part (Rel-17, CAT F) |
MCC, CATT |
R4-2211319 |
Big CR for TS 38.141-2 Maintenance RF part (Rel-15, CAT F) |
MCC, Huawei |
R4-2211320 |
Big CR for TS 38.141-2 Maintenance RF part (Rel-16, CAT F) |
MCC, Huawei |
R4-2211321 |
Big CR for TS 38.141-2 Maintenance RF part (Rel-17, CAT F) |
MCC, Huawei |
4.1.2.1 |
General |
|
R4-2207704 |
draft CR 38.104 to address compliance for spurious emissions in C-band in the US for non-contiguous aggregation between 3.45-3.55 MHz and 3.7-3.98 MHz |
Charter Communications, Inc |
R4-2207705 |
Additional BS Spurious emissions for Band n77 |
Charter Communications, Inc |
R4-2208535 |
Technical background related to sub-array parameters relevant for 6 to 10 GHz |
Ericsson |
R4-2208536 |
CR to TR 38.921: Addition of additional BS antenna parameters in subclause 8.1 |
Ericsson |
R4-2209608 |
Additional BS Spurious emissions for Band n77 |
Charter Communications, Inc |
R4-2209646 |
Draft CR to TS 38.104: NR frequency band table notes corrections, Rel-16 |
Huawei, HiSilicon |
R4-2209647 |
Draft CR to TS 38.104: NR frequency band table notes corrections, Rel-17 |
Huawei, HiSilicon |
R4-2210692 |
draft CR 38.104 to address compliance for spurious emissions in C-band in the US for non-contiguous aggregation between 3.45-3.55 MHz and 3.7-3.98 MHz |
Charter Communications, Inc |
4.1.2.2 |
TX/RX requirements (38.104) |
|
R4-2207911 |
Draft CR to TS 38.104 on clarifications of interfering signal for the OTA transmitter intermodulation requirement |
Nokia, Nokia Shanghai Bell, Ericsson, Huawei |
R4-2207912 |
Draft CR to TS 38.104 on clarifications of interfering signal for the OTA transmitter intermodulation requirement |
Nokia, Nokia Shanghai Bell, Ericsson, Huawei |
R4-2207913 |
Draft CR to TS 38.104 on clarifications of interfering signal for the OTA transmitter intermodulation requirement |
Nokia, Nokia Shanghai Bell, Ericsson, Huawei |
R4-2209648 |
Draft CR to TS 38.104: Additional Tx spurious emissions terminology corrections (basic limit, maximum level, minimum requirement), Rel-16 |
Huawei, HiSilicon |
R4-2209649 |
Draft CR to TS 38.104: Additional Tx spurious emissions terminology corrections (basic limit, maximum level, minimum requirement), Rel-17 |
Huawei, HiSilicon |
R4-2209810 |
Draft CR to TS 38.104 with clarifications of BS type for band n96 |
Nokia, Nokia Shanghai Bell |
R4-2209811 |
Draft CR to TS 38.104 with clarifications of BS type for band n96 and n102 |
Nokia, Nokia Shanghai Bell |
4.1.2.3 |
MSR and eAAS specifications |
|
R4-2207914 |
Draft CR to TS 37.141 on corrections of test configurations |
Nokia, Nokia Shanghai Bell |
R4-2207915 |
Draft CR to TS 37.141 on corrections of test configurations |
Nokia, Nokia Shanghai Bell |
R4-2207916 |
Draft CR to TS 37.145-1 on corrections of test configurations |
Nokia, Nokia Shanghai Bell |
R4-2207917 |
Draft CR to TS 37.145-1 on corrections of test configurations |
Nokia, Nokia Shanghai Bell |
R4-2207918 |
Draft CR to TS 37.145-2 on corrections of test configurations |
Nokia, Nokia Shanghai Bell |
R4-2207919 |
Draft CR to TS 37.145-2 on corrections of test configurations |
Nokia, Nokia Shanghai Bell |
R4-2209729 |
CR to 37.104: Corrections to notes in OBUE requirements |
Nokia, Nokia Shanghai Bell |
R4-2209730 |
CR to 37.104: Corrections to notes in OBUE requirements |
Nokia, Nokia Shanghai Bell |
R4-2209731 |
CR to 37.104: Corrections to notes in OBUE requirements |
Nokia, Nokia Shanghai Bell |
R4-2209732 |
CR to 37.141: Corrections to notes in OBUE requirements |
Nokia, Nokia Shanghai Bell |
R4-2209733 |
CR to 37.141: Corrections to notes in OBUE requirements |
Nokia, Nokia Shanghai Bell |
R4-2209734 |
CR to 37.141: Corrections to notes in OBUE requirements |
Nokia, Nokia Shanghai Bell |
R4-2210023 |
Draft CR to TS 37.105 on clarifications of interfering signal for the OTA transmitter intermodulation requirement (REL15) |
Huawei, Nokia, Ericsson |
R4-2210024 |
Draft CR to TS 37.105 on clarifications of interfering signal for the OTA transmitter intermodulation requirement (REL16) |
Huawei, Nokia, Ericsson |
R4-2210025 |
Draft CR to TS 37.105 on clarifications of interfering signal for the OTA transmitter intermodulation requirement (REL17) |
Huawei, Nokia, Ericsson |
R4-2210026 |
Draft CR to TS 37.145-2 on clarifications of interfering signal for the OTA transmitter intermodulation requirement (REL15) |
Huawei, Nokia, Ericsson |
R4-2210027 |
Draft CR to TS 37.145-2 on clarifications of interfering signal for the OTA transmitter intermodulation requirement (REL16) |
Huawei, Nokia, Ericsson |
R4-2210028 |
Draft CR to TS 37.145-2 on clarifications of interfering signal for the OTA transmitter intermodulation requirement (REL17) |
Huawei, Nokia, Ericsson |
R4-2210693 |
Draft CR to TS 37.145-2 on clarifications of interfering signal for the OTA transmitter intermodulation requirement (REL15) |
Huawei |
R4-2210694 |
CR to 37.141: Corrections to notes in OBUE requirements |
Nokia, Nokia Shanghai Bell |
4.1.3 |
BS conformance testing |
|
R4-2210308 |
Email discussion summary for [103-e][302] NR_Conformance_Maintenance |
Moderator (Huawei) |
R4-2210505 |
Email discussion summary for [103-e][302] NR_Conformance_Maintenance |
Moderator (Huawei) |
4.1.3.1 |
General |
|
R4-2208121 |
Draft CR for TS 38.176-2 R16: correction of the co-existence test requirements |
CATT |
R4-2208123 |
Draft CR for TS 38.176-1 R16: add the missing contents of A.1.1 |
CATT |
R4-2208124 |
Draft CR for TS 38.176-1 R17: add the missing contents of A.1.1 |
CATT |
R4-2208125 |
Draft CR for TS 38.176-2 R16: add the missing contents of A.1.1 |
CATT |
R4-2208126 |
Draft CR for TS 38.176-2 R17: add the missing contents of A.1.1 |
CATT |
R4-2210696 |
Draft CR for TS 38.176-2 R16: correction of the co-existence test requirements |
CATT |
R4-2211324 |
Big CR for TS 38.176-1 Maintenance (Rel-16, CAT F) |
MCC, Huawei |
R4-2211325 |
Big CR for TS 38.176-1 Maintenance (Rel-17, CAT F) |
MCC, Huawei |
R4-2211326 |
Big CR for TS 38.176-2 Maintenance (Rel-16, CAT F) |
MCC, Nokia |
R4-2211327 |
Big CR for TS 38.176-2 Maintenance (Rel-17, CAT F) |
MCC, Nokia |
4.1.3.2 |
Conducted conformance testing (38.141-1) |
|
R4-2209812 |
Draft CR to TS 38.141-1 with clarifications of BS type for band n96 |
Nokia, Nokia Shanghai Bell |
R4-2209813 |
Draft CR to TS 38.141-1 with clarifications of BS type for band n96 and n102 |
Nokia, Nokia Shanghai Bell |
4.1.3.3 |
Radiated conformance testing (38.141-2) |
|
R4-2208127 |
Draft CR for TS 38.141-2 R15: correction of declaration descriptions |
CATT |
R4-2208128 |
Draft CR for TS 38.141-2 R16: correction of BS type 1-O co-existence table |
CATT |
R4-2208231 |
CR for TS 38.141-2 On sweep time for unwanted emission testing (Rel-15) |
CATT |
R4-2208232 |
CR for TS 38.141-2 On sweep time for unwanted emission testing (Rel-16) |
CATT |
R4-2208233 |
CR for TS 38.141-2 On sweep time for unwanted emission testing (Rel-17) |
CATT |
R4-2208234 |
CR for TS 36.141 On sweep time for unwanted emission testing (Rel-15) |
CATT |
R4-2208235 |
CR for TS 36.141 On sweep time for unwanted emission testing (Rel-16) |
CATT |
R4-2208236 |
CR for TS 36.141 On sweep time for unwanted emission testing (Rel-17) |
CATT |
R4-2209080 |
CR for TS 37.141 On sweep time for unwanted emission testing (Rel-15) |
CATT |
R4-2209081 |
CR for TS 37.141 On sweep time for unwanted emission testing (Rel-16) |
CATT |
R4-2209082 |
CR for TS 37.141 On sweep time for unwanted emission testing (Rel-17) |
CATT |
R4-2209650 |
Draft CR to TS 38.141-2: removal of Editor's notes, Rel-15 |
Huawei, HiSilicon |
R4-2209651 |
Draft CR to TS 38.141-2: removal of Editor's notes, Rel-16 |
Huawei, HiSilicon |
R4-2209652 |
Draft CR to TS 38.141-2: removal of Editor's notes, Rel-17 |
Huawei, HiSilicon |
R4-2210031 |
Draft CR to TS 38.141-2 on clarifications of interfering signal for the OTA transmitter intermodulation requirement |
Ericsson, Huawei, Nokia, Nokia Shanghai Bell |
R4-2210032 |
Draft CR to TS 38.141-2 on clarifications of interfering signal for the OTA transmitter intermodulation requirement |
Ericsson, Huawei, Nokia, Nokia Shanghai Bell |
R4-2210033 |
Draft CR to TS 38.141-2 on clarifications of interfering signal for the OTA transmitter intermodulation requirement |
Ericsson, Huawei, Nokia, Nokia Shanghai Bell |
R4-2210817 |
CR for TS 36.141 On sweep time for unwanted emission testing (Rel-15) |
CATT |
R4-2210820 |
CR for TS 37.141 On sweep time for unwanted emission testing (Rel-15) |
CATT |
R4-2210821 |
CR for TS 38.141-2 On sweep time for unwanted emission testing (Rel-15) |
CATT |
R4-2210822 |
Draft CR for TS 38.141-2 R16: correction of BS type 1-O co-existence table |
CATT |
4.1.3.4 |
OAT BS testing |
|
R4-2208564 |
Draft CR to 37.145-1: Clarification for unwanted emission testing |
Huawei, HiSilicon |
R4-2208565 |
Draft CR to 37.145-1: Clarification for unwanted emission testing |
Huawei, HiSilicon |
R4-2208566 |
Draft CR to 37.145-1: Clarification for unwanted emission testing |
Huawei, HiSilicon |
R4-2208567 |
Draft CR to 37.145-2: Clarification for unwanted emission testing |
Huawei, HiSilicon |
R4-2208568 |
Draft CR to 37.145-2: Clarification for unwanted emission testing |
Huawei, HiSilicon |
R4-2208569 |
Draft CR to 37.145-2: Clarification for unwanted emission testing |
Huawei, HiSilicon |
R4-2210818 |
Draft CR to 37.145-1: Clarification for unwanted emission testing |
Huawei, HiSilicon |
R4-2210819 |
Draft CR to 37.145-2: Clarification for unwanted emission testing |
Huawei, HiSilicon |
4.1.4 |
UE/BS EMC requirements |
|
R4-2207894 |
TS 38.175: Corrections in clause 1 Scope and clause 9 Immunity |
Ericsson |
R4-2207895 |
TS 36.113: Corrections in clause 9 Immunity |
Ericsson |
R4-2207896 |
TS 36.113: Corrections in clause 9 Immunity |
Ericsson |
R4-2207897 |
TS 37.113: Corrections in clause 9 Immunity |
Ericsson |
R4-2207898 |
TS 37.113: Corrections in clause 9 Immunity |
Ericsson |
R4-2207899 |
TS 37.114: Corrections in clause 1 Scope and clause 9 Immunity |
Ericsson |
R4-2207900 |
TS 37.114: Corrections in clause 1 Scope and clause 9 Immunity |
Ericsson |
R4-2207901 |
TS 38.113: Corrections in clause 1 Scope and clause 9 Immunity |
Ericsson |
R4-2207902 |
TS 38.113: Corrections in clause 1 Scope and clause 9 Immunity |
Ericsson |
R4-2208380 |
Discussion on highest frequency and measurement uncertainty for NR BS radiated emission test with big size EUT |
ZTE Corporation |
R4-2208382 |
Draft CR to TS 38.113 Radiated emission measurement uncertainty (R15) |
ZTE Corporation |
R4-2208384 |
Draft CR to TS 38.113 Radiated emission measurement uncertainty (R16) |
ZTE Corporation |
R4-2208386 |
Draft CR to TS 38.113 Radiated emission measurement uncertainty (R17) |
ZTE Corporation |
R4-2209653 |
CR to TS 34.124: corrections of the UTRA UE EMC specification, Rel-17 |
Huawei, HiSilicon |
R4-2209654 |
Draft CR to TS 38.124: addition of the missing Rx spurious emissions limits for idle mode testing, Rel-15 |
Huawei, HiSilicon, Samsung |
R4-2209655 |
Draft CR to TS 38.124: addition of the missing Rx spurious emissions limits for idle mode testing, Rel-16 |
Huawei, HiSilicon, Samsung |
R4-2209656 |
Draft CR to TS 38.124: addition of the missing Rx spurious emissions limits for idle mode testing, Rel-17 |
Huawei, HiSilicon, Samsung |
R4-2209657 |
Draft CR to TS 36.124: correction of the Rx spurious exclusion band (band-agnostic), Rel-8 |
Huawei, HiSilicon |
R4-2209658 |
Draft CR to TS 36.124: correction of the Rx spurious exclusion band (band-agnostic), Rel-9 |
Huawei, HiSilicon |
R4-2209659 |
Draft CR to TS 36.124: correction of the Rx spurious exclusion band (band-agnostic), Rel-10 |
Huawei, HiSilicon |
R4-2209660 |
Draft CR to TS 36.124: correction of the Rx spurious exclusion band (band-agnostic), Rel-11 |
Huawei, HiSilicon |
R4-2209661 |
Draft CR to TS 36.124: correction of the Rx spurious exclusion band (band-agnostic), Rel-12 |
Huawei, HiSilicon |
R4-2209662 |
Draft CR to TS 36.124: correction of the Rx spurious exclusion band (band-agnostic), Rel-13 |
Huawei, HiSilicon |
R4-2209663 |
Draft CR to TS 36.124: correction of the Rx spurious exclusion band (band-agnostic), Rel-14 |
Huawei, HiSilicon |
R4-2209664 |
Draft CR to TS 36.124: correction of the Rx spurious exclusion band (band-agnostic), Rel-15 |
Huawei, HiSilicon |
R4-2209665 |
Draft CR to TS 36.124: correction of the Rx spurious exclusion band (band-agnostic), Rel-16 |
Huawei, HiSilicon |
R4-2209666 |
CR to TS 38.175: updates reflecting modifications in IEC 61000-4-3:2020 for the upper frequency range of the RI test |
Huawei, HiSilicon |
R4-2209667 |
Draft CR to TS 36.124: correction of the Rx spurious exclusion band (band-agnostic), Rel-17 |
Huawei, HiSilicon |
R4-2209668 |
Further analysis of the updated IEC 61000-4-3:2020 specification: upper frequency range for radiated immunity requirements |
Huawei, HiSilicon |
R4-2209669 |
CR to TS 38.113: updates reflecting modifications in IEC 61000-4-3:2020 for the upper frequency range of the RI test |
Huawei, HiSilicon |
R4-2209670 |
CR to TS 38.124: updates reflecting modifications in IEC 61000-4-3:2020 for the upper frequency range of the RI test, Rel-17 |
Huawei, HiSilicon |
R4-2209671 |
CR to TS 38.114: updates reflecting modifications in IEC 61000-4-3:2020 for the upper frequency range of the RI test, Rel-17 |
Huawei, HiSilicon |
R4-2210044 |
TS 38.175: Corrections in clause 1 Scope and clause 9 Immunity |
Ericsson |
R4-2210045 |
TS 36.113: Corrections in clause 9 Immunity |
Ericsson |
R4-2210046 |
TS 37.113: Corrections in clause 9 Immunity |
Ericsson |
R4-2210047 |
TS 37.114: Corrections in clause 1 Scope and clause 9 Immunity |
Ericsson |
R4-2210048 |
TS 38.113: Corrections in clause 1 Scope and clause 9 Immunity |
Ericsson |
R4-2210309 |
Email discussion summary for [103-e][303] NR_EMC |
Moderator (ZTE Corporation) |
R4-2210506 |
Email discussion summary for [103-e][303] NR_EMC |
Moderator (ZTE Corporation) |
R4-2210627 |
WF on 6 GHz limit for the Radiated Immunity testing |
Huawei |
R4-2210628 |
WF on the criteria for performance assessment for NR Repeater EMC testing |
ZTE |
R4-2210823 |
TS 38.175: Corrections in clause 1 Scope and clause 9 Immunity |
Ericsson |
R4-2210824 |
TS 36.113: Corrections in clause 9 Immunity |
Ericsson |
R4-2210825 |
TS 37.113: Corrections in clause 9 Immunity |
Ericsson |
R4-2210826 |
TS 37.114: Corrections in clause 1 Scope and clause 9 Immunity |
Ericsson |
R4-2211141 |
TS 38.113: Corrections in clause 1 Scope and clause 9 Immunity |
Ericsson |
R4-2211181 |
Draft CR to TS 38.113 Radiated emission measurement uncertainty (R15) |
ZTE Corporation |
4.1.5 |
RRM requirements |
|
R4-2208198 |
Draft CR on TS 36.171 requirements for support of A-GNSS |
CATT, CAICT, CENC |
R4-2208199 |
Draft CR on TS 36.171 requirements for support of A-GNSS |
CATT, CAICT, CENC |
R4-2208200 |
Draft CR on TS 38.171 requirements for support of A-GNSS |
CATT, CAICT, CENC |
R4-2208201 |
Draft CR on TS 38.171 requirements for support of A-GNSS |
CATT, CAICT, CENC |
R4-2210273 |
Email discussion summary for [103-e][201] Maintenance_R15_R16_RRM |
Moderator (Huawei) |
R4-2210470 |
Email discussion summary for [103-e][201] Maintenance_R15_R16_RRM |
Moderator (Huawei) |
R4-2210581 |
WF on R15 and R16 RRM maintenance |
Huawei, Hisilicon |
R4-2211210 |
WF on R15 and R16 RRM maintenance |
Huawei, Hisilicon |
4.1.5.1 |
RRM core requirements (38.133/36.133) |
|
R4-2207787 |
CR for eMIMO requirements maintenance (Rel-16) |
Apple |
R4-2207788 |
CR for eMIMO requirements maintenance (Rel-17) |
Apple |
R4-2207875 |
Maintenance CR for RRM requirements on 38.133 R16 |
MediaTek (Shenzhen) Inc. |
R4-2207876 |
Maintenance CR for RRM requirements on 38.133 R17 |
MediaTek (Shenzhen) Inc. |
R4-2207877 |
Maintenance CR for V2X Te requirements on 38.133 R16 |
MediaTek (Shenzhen) Inc. |
R4-2207878 |
Maintenance CR for V2X Te requirements on 38.133 R17 |
MediaTek (Shenzhen) Inc. |
R4-2207941 |
draft Cat-F CR (R15) to SCell Activation Core |
Qualcomm Incorporated |
R4-2207942 |
draft Cat-A CR (R16) to SCell Activation Core |
Qualcomm Incorporated |
R4-2207943 |
draft Cat-A CR (R17) to SCell Activation Core |
Qualcomm Incorporated |
R4-2207944 |
draft Cat-F CR (R16) to SCell Activation Core |
Qualcomm Incorporated |
R4-2207945 |
draft Cat-A CR (R17) to SCell Activation Core |
Qualcomm Incorporated |
R4-2207946 |
draft Cat-F CR (R16) to SCell Activation Core NR-U |
Qualcomm Incorporated |
R4-2207947 |
draft Cat-A CR (R17) to SCell Activation Core NR-U |
Qualcomm Incorporated |
R4-2208829 |
Draft CR to TS 38.133 Correction to Rel-16 IDLE CA&DC measurements requirements |
vivo |
R4-2208830 |
Draft CR to TS 38.133 Correction to Rel-17 IDLE CA&DC measurements requirements |
vivo |
R4-2208831 |
Draft CR to TS 36.133 Correction to IDLE DC measurements requirements_R16 |
vivo |
R4-2208832 |
Draft CR to TS 36.133 Correction to IDLE DC measurements requirements_R17 |
vivo |
R4-2208836 |
Draft CR to 38.133 correction to NR positioning measurement requirements |
vivo |
R4-2208837 |
Draft CR to 38.133 correction to NR positioning measurement requirements |
vivo |
R4-2208848 |
CR to TS38.133 for the editorial correction on L1-SINR scheduling restriction |
Samsung |
R4-2208849 |
CR to TS38.133 for the editorial correction on L1-SINR scheduling restriction |
Samsung |
R4-2208909 |
Correction to NR SCell activation interruption requirements 38133_r15 |
Huawei, Hisilicon |
R4-2208910 |
Correction to NR SCell activation interruption requirements 38133_r16 |
Huawei, Hisilicon |
R4-2208911 |
Correction to NR SCell activation interruption requirements 38133_r17 |
Huawei, Hisilicon |
R4-2208912 |
Correction to NR SCell activation interruption requirements 36133_r15 |
Huawei, Hisilicon |
R4-2208913 |
Correction to NR SCell activation interruption requirements 36133_r16 |
Huawei, Hisilicon |
R4-2208914 |
Correction to NR SCell activation interruption requirements 36133_r17 |
Huawei, Hisilicon |
R4-2208915 |
Correction to paging interruption during reselection requirements_r15 |
Huawei, Hisilicon |
R4-2208916 |
Correction to paging interruption during reselection requirements_r16 |
Huawei, Hisilicon |
R4-2208917 |
Correction to paging interruption during reselection requirements_r17 |
Huawei, Hisilicon |
R4-2208922 |
Correction to HST inter-RAT NR cell reselection requirements_r16 |
Huawei, Hisilicon |
R4-2208923 |
Correction to HST inter-RAT NR cell reselection requirements_r17 |
Huawei, Hisilicon |
R4-2208924 |
Correction to HST intra-NR cell-reselection requirements_r16 |
Huawei, Hisilicon |
R4-2208925 |
Correction to HST intra-NR cell-reselection requirements_r17 |
Huawei, Hisilicon |
R4-2208927 |
Draft CR on requirements maintenance for NR-U 36133 R16 |
Huawei, Hisilicon |
R4-2208928 |
Draft CR on requirements maintenance for NR-U 36133 R17 |
Huawei, Hisilicon |
R4-2208929 |
Draft CR on requirements maintenance for NR-U 38133 R16 |
Huawei, Hisilicon |
R4-2208930 |
Draft CR on requirements maintenance for NR-U 38133 R17 |
Huawei, Hisilicon |
R4-2208931 |
Draft CR on maintenance for IAB R16 |
Huawei, Hisilicon |
R4-2208932 |
Draft CR on maintenance for IAB R17 |
Huawei, Hisilicon |
R4-2208933 |
Draft CR on adding NR bands groups for NB-IoT R16 |
Huawei, Hisilicon |
R4-2208934 |
Draft CR on adding NR bands groups for NB-IoT R17 |
Huawei, Hisilicon |
R4-2208956 |
Clarification on asynchronous DAPS handover R16 |
Huawei, Hisilicon |
R4-2208957 |
Clarification on asynchronous DAPS handover R17 |
Huawei, Hisilicon |
R4-2208987 |
Discussion on maintaining PL-RS switching delay requirements in R16 |
Huawei, Hisilicon |
R4-2208988 |
DraftCR on maintaining PL-RS switching delay requirements R16 |
Huawei, Hisilicon |
R4-2208989 |
DraftCR on maintaining PL-RS switching delay requirements R17 |
Huawei, Hisilicon |
R4-2209186 |
CR on CSSF outside MG R15 |
Huawei, Hisilicon |
R4-2209187 |
CR on CSSF outside MG R16 |
Huawei, Hisilicon |
R4-2209188 |
CR on CSSF outside MG R17 |
Huawei, Hisilicon |
R4-2209189 |
CR on beam level EMR requirements 36133 R16 |
Huawei, Hisilicon |
R4-2209190 |
CR on beam level EMR requirements 36133 R17 |
Huawei, Hisilicon |
R4-2209191 |
CR on beam level EMR requirements 38133 R16 |
Huawei, Hisilicon |
R4-2209192 |
CR on beam level EMR requirements 38133 R17 |
Huawei, Hisilicon |
R4-2209193 |
Discussion on remaining issues in PRS measurement period |
Huawei, Hisilicon |
R4-2209194 |
CR on PRS meausurement period R16 |
Huawei, Hisilicon |
R4-2209195 |
CR on PRS meausurement period R17 |
Huawei, Hisilicon |
R4-2209199 |
CR to multiple SCell activation requirements R16 |
Huawei, Hisilicon |
R4-2209200 |
CR to multiple SCell activation requirements R17 |
Huawei, Hisilicon |
R4-2209201 |
CR on CGI reading requirements R16 |
Huawei, Hisilicon |
R4-2209202 |
CR on CGI reading requirements R17 |
Huawei, Hisilicon |
R4-2210958 |
draft Cat-F CR (R15) to SCell Activation Core |
Qualcomm Incorporated |
R4-2210959 |
draft Cat-F CR (R16) to SCell Activation Core |
Qualcomm Incorporated |
R4-2210960 |
draft Cat-F CR (R16) to SCell Activation Core NR-U |
Qualcomm Incorporated |
R4-2210961 |
Draft CR to 38.133 correction to NR positioning measurement requirements |
vivo |
R4-2210962 |
Correction to NR SCell activation interruption requirements 38133_r15 |
Huawei, Hisilicon |
R4-2210963 |
Correction to NR SCell activation interruption requirements 36133_r15 |
Huawei, Hisilicon |
R4-2210964 |
Correction to paging interruption during reselection requirements_r16 |
Huawei, Hisilicon |
R4-2210965 |
Correction to HST inter-RAT NR cell reselection requirements_r16 |
Huawei, Hisilicon |
R4-2210966 |
Correction to HST intra-NR cell-reselection requirements_r16 |
Huawei, Hisilicon |
R4-2210967 |
DraftCR on maintaining PL-RS switching delay requirements R16 |
Huawei, Hisilicon |
R4-2210968 |
CR on beam level EMR requirements 36133 R16 |
Huawei, Hisilicon |
R4-2210969 |
CR on PRS meausurement period R16 |
Huawei, Hisilicon |
R4-2210970 |
CR on beam level EMR requirements 38133 R16 |
Huawei, Hisilicon |
R4-2210971 |
CR to multiple SCell activation requirements R16 |
Huawei, Hisilicon |
R4-2211164 |
Maintenance CR for RRM requirements on 38.133 R16 |
MediaTek (Shenzhen) Inc. |
R4-2211197 |
Correction to paging interruption during reselection requirements_r15 |
Huawei, Hisilicon |
R4-2211211 |
Draft CR to 38.133 correction to NR positioning measurement requirements |
vivo |
R4-2211230 |
Big CR for TS 38.133 Core Maintenance Part-1 (Rel-15) |
MCC, Apple |
R4-2211231 |
Big CR for TS 38.133 Core Maintenance Part-1 (Rel-16) |
MCC, Apple |
R4-2211232 |
Big CR for TS 38.133 Core Maintenance Part-2 (Rel-17) |
MCC, Apple |
R4-2211233 |
Big CR for TS 38.133 Core Maintenance Part-2 (Rel-15) |
MCC, Ericsson |
R4-2211234 |
Big CR for TS 38.133 Core Maintenance Part-2 (Rel-16) |
MCC, Ericsson |
R4-2211235 |
Big CR for TS 38.133 Core Maintenance Part-2 (Rel-17) |
MCC, Ericsson |
R4-2211242 |
Big CR on TS 38.174 Maintenance (Rel-16) |
MCC, ZTE |
R4-2211243 |
Big CR on TS 38.174 Maintenance (Rel-17) |
MCC, ZTE |
R4-2211322 |
Big CR for TS 38.174 Maintenance (Rel-16, CAT F) |
MCC, CATT |
R4-2211323 |
Big CR for TS 38.174 Maintenance (Rel-17, CAT F) |
MCC, CATT |
R4-2211334 |
Big CR on TS 36.133 Maintenance (Rel-16) |
MCC, Xiaomi |
R4-2211335 |
Big CR on TS 36.133 Maintenance (Rel-17) |
MCC, Xiaomi |
R4-2211336 |
Big CR on TS 38.174 Maintenance (Rel-16) |
MCC, ZTE |
R4-2211337 |
Big CR on TS 38.174 Maintenance (Rel-17) |
MCC, ZTE |
R4-2211340 |
Big CR on TS 36.133 Maintenance (Rel-14) |
MCC, Xiaomi |
R4-2211341 |
Big CR on TS 36.133 Maintenance (Rel-15) |
MCC, Xiaomi |
R4-2211345 |
Big CR for TS 38.174 Maintenance (Rel-16, CAT F) |
MCC, CATT |
R4-2211346 |
Big CR for TS 38.174 Maintenance (Rel-17, CAT F) |
MCC, CATT |
4.1.5.2 |
RRM performance requirements (38.133/36.133) |
|
R4-2207646 |
Draft CR to FR1 DCI-based BWP switch TCs |
Anritsu Corporation |
R4-2207647 |
Draft CR to FR1 DCI-based BWP switch TCs |
Anritsu Corporation |
R4-2207648 |
Draft CR to FR1 DCI-based BWP switch TCs and FR2 CSI-RS based RLM |
Anritsu Corporation |
R4-2207649 |
Draft CR to Cell reselection to FR1 intra-frequency NR case |
Anritsu Corporation |
R4-2207650 |
Draft CR to Cell reselection to FR1 intra-frequency NR case |
Anritsu Corporation |
R4-2207747 |
On RRM performance maintenance |
Apple |
R4-2207748 |
draftCR on applicabiltiy for test Cases involving E-UTRA/FR1 and FR2 carriers (R15) |
Apple |
R4-2207749 |
draftCR on applicabiltiy for test Cases involving E-UTRA/FR1 and FR2 carriers (R16) |
Apple |
R4-2207750 |
draftCR on applicabiltiy for test Cases involving E-UTRA/FR1 and FR2 carriers (R17) |
Apple |
R4-2207789 |
CR for Spatial relation info switch testcase maintenance (Rel-16) |
Apple |
R4-2207790 |
CR for Spatial relation info switch testcase maintenance (Rel-17) |
Apple |
R4-2207948 |
draft Cat-F CR (R15) to SCell Activation Test Cases |
Qualcomm Incorporated |
R4-2207949 |
draft Cat-A CR (R16) to SCell Activation Test Cases |
Qualcomm Incorporated |
R4-2207950 |
draft Cat-A CR (R17) to SCell Activation Test Cases |
Qualcomm Incorporated |
R4-2207951 |
draft Cat-F CR (R16) to SCell Activation Test Cases and SRS configuration |
Qualcomm Incorporated |
R4-2207952 |
draft Cat-A CR (R17) to SCell Activation Test Cases and SRS configuration |
Qualcomm Incorporated |
R4-2207953 |
draft Cat-F CR (R16) to SCell Activation Test Cases NR-U |
Qualcomm Incorporated |
R4-2207954 |
draft Cat-A CR (R17) to SCell Activation Test Cases NR-U |
Qualcomm Incorporated |
R4-2208024 |
Remaining issues in NR positioning performance requirements |
Qualcomm Incorporated |
R4-2208162 |
Draft CR on HST FR1 L1-RSRP test cases |
CATT |
R4-2208163 |
Draft CR on HST FR1 L1-RSRP test cases |
CATT |
R4-2208164 |
Draft CR on test case for cell reselection for power saving |
CATT |
R4-2208165 |
Draft CR on test case for cell reselection for power saving |
CATT |
R4-2208166 |
Draft CR to add missing SMTC pattern |
CATT |
R4-2208167 |
Draft CR on radio link monitoring test cases in FR1 |
CATT |
R4-2208168 |
Draft CR on radio link monitoring test cases in FR1 |
CATT |
R4-2208169 |
Draft CR on radio link monitoring test cases in FR1 |
CATT |
R4-2208202 |
Draft CR on R16 NR positioning test cases of general configurations and measurement delay requirements |
CATT |
R4-2208203 |
Draft CR on R16 NR positioning test cases of general configurations and measurement delay requirements |
CATT |
R4-2208204 |
Draft CR on R16 NR positioning test case of accuracy requirements |
CATT |
R4-2208205 |
Draft CR on R16 NR positioning test case of accuracy requirements |
CATT |
R4-2208341 |
CR to maintain test case of PScell addition and release delay (A4.5.7)_R15 |
OPPO |
R4-2208342 |
CR to maintain test case of PScell addition and release delay (A4.5.7)_R16 |
OPPO |
R4-2208343 |
CR to maintain test case of PScell addition and release delay (A4.5.7)_R17 |
OPPO |
R4-2208344 |
CR to maintain inter-RAT measurements subject to CCA in TS 36.133(R16) |
OPPO |
R4-2208345 |
CR to maintain inter-RAT measurements subject to CCA in TS 36.133(R17) |
OPPO |
R4-2208469 |
Discussion on FR2 inter-frequency relative RSRP accuracy |
MediaTek Inc. |
R4-2208734 |
[dCR] Maintenance for IAB-MT test cases R16 |
ZTE Corporation |
R4-2208735 |
[dCR] Maintenance for IAB-MT test cases R17 Cat A |
ZTE Corporation |
R4-2208833 |
Remaining issues on measurement accuracy requirements for Rel-16 NR positioning |
vivo |
R4-2208834 |
Draft CR to 38.133 correction to NR positioning accuracy requirements |
vivo |
R4-2208835 |
Draft CR to 38.133 correction to NR positioning accuracy requirements |
vivo |
R4-2208879 |
FR2 Inter-frequency Relative SS-RSRP accuracy |
Anritsu Corporation |
R4-2208906 |
Correction to cell reselection test case_r15 |
Huawei, Hisilicon |
R4-2208907 |
Correction to cell reselection test case_r16 |
Huawei, Hisilicon |
R4-2208908 |
Correction to cell reselection test case_r17 |
Huawei, Hisilicon |
R4-2208918 |
Correction to SRS reference configuration_r16 |
Huawei, Hisilicon |
R4-2208919 |
Correction to SRS reference configuration_r17 |
Huawei, Hisilicon |
R4-2208920 |
Correction to eMIMO BFD test cases_r16 |
Huawei, Hisilicon |
R4-2208921 |
Correction to eMIMO BFD test cases_r17 |
Huawei, Hisilicon |
R4-2208926 |
Discussion on issues on Rel-15 test cases |
Huawei, Hisilicon |
R4-2208985 |
Update to UL switching test cases |
Huawei, Hisilicon |
R4-2208986 |
Update to UL switching test cases |
Huawei, Hisilicon |
R4-2208990 |
DraftCR on maintaining L1-SINR measurement test cases R16 |
Huawei, Hisilicon |
R4-2208991 |
DraftCR on maintaining L1-SINR measurement test cases R17 |
Huawei, Hisilicon |
R4-2209076 |
draft CR: Correction of NR-U RRM test cases |
Ericsson |
R4-2209077 |
draft CR: Correction of NR-U RRM test cases |
Ericsson |
R4-2209078 |
draft CR: Correction of PRACH configuration parameter for inter-RAT test |
Ericsson |
R4-2209079 |
draft CR: Correction of PRACH configuration parameter for inter-RAT test |
Ericsson |
R4-2209196 |
Discussion on accuracy requirements for positioning measurement |
Huawei, Hisilicon |
R4-2209197 |
CR on accuracy requirements for positioning measurement R16 |
Huawei, Hisilicon |
R4-2209198 |
CR on accuracy requirements for positioning measurement R17 |
Huawei, Hisilicon |
R4-2209609 |
Draft CR to TS 38.133: Corrections to intra-frequency event triggered test cases (Rel 15) |
Rohde & Schwarz |
R4-2209610 |
Draft CR to TS 38.133: Corrections to intra-frequency event triggered test cases (Rel 16) |
Rohde & Schwarz |
R4-2209611 |
Draft CR to TS 38.133: Corrections to intra-frequency event triggered test cases (Rel 17) |
Rohde & Schwarz |
R4-2209612 |
Draft CR to TS 38.133: Corrections to beam failure and link recovery test cases (Rel 15) |
Rohde & Schwarz |
R4-2209613 |
Draft CR to TS 38.133: Corrections to beam failure and link recovery test cases (Rel 16) |
Rohde & Schwarz |
R4-2209614 |
Draft CR to TS 38.133: Corrections to beam failure and link recovery test cases (Rel 17) |
Rohde & Schwarz |
R4-2210084 |
CR: Corrections on NR V2X Resource Selection Test |
Qualcomm, Inc. |
R4-2210085 |
(mirror R17)CR: Corrections on NR V2X Resource Selection Test |
Qualcomm, Inc. |
R4-2210086 |
CR: Corrections on LTE V2X Resource Selection Test |
Qualcomm, Inc. |
R4-2210087 |
(mirror R15)Corrections on LTE V2X Resource Selection Test |
Qualcomm, Inc. |
R4-2210088 |
(mirror R16)Corrections on LTE V2X Resource Selection Test |
Qualcomm, Inc. |
R4-2210089 |
(mirror R17)Corrections on LTE V2X Resource Selection Test |
Qualcomm, Inc. |
R4-2210091 |
Draft CR 38.133 on DAPS handover test case |
MediaTek Inc. |
R4-2210107 |
Draft CR 38.133 on DAPS handover test case |
MediaTek Inc. |
R4-2210181 |
On UE positioning performance requirements |
Ericsson |
R4-2210182 |
Updates to accuracy requirements for UE positioning measurements in TS 38.133 |
Ericsson |
R4-2210183 |
Updates to accuracy requirements for UE positioning measurements in TS 38.133 |
Ericsson |
R4-2210184 |
Correction to conditions for NR PRS-based measurements in TS 38.133 |
Ericsson |
R4-2210185 |
Correction to conditions for NR PRS-based measurements in TS 38.133 |
Ericsson |
R4-2210225 |
DraftCR - Correction of margins for UE Rx-Tx accuracy requirements |
Qualcomm Incorporated |
R4-2210972 |
draftCR on applicabiltiy for test Cases involving E-UTRA/FR1 and FR2 carriers (R15) |
Apple |
R4-2210973 |
CR for Spatial relation info switch testcase maintenance (Rel-16) |
Apple |
R4-2210974 |
draft Cat-F CR (R16) to SCell Activation Test Cases and SRS configuration |
Qualcomm Incorporated |
R4-2210975 |
Draft CR on HST FR1 L1-RSRP test cases |
CATT |
R4-2210976 |
Draft CR on R16 NR positioning test cases of general configurations and measurement delay requirements |
CATT |
R4-2210977 |
Draft CR on R16 NR positioning test case of accuracy requirements |
CATT |
R4-2210978 |
CR to maintain test case of PScell addition and release delay (A4.5.7)_R15 |
OPPO |
R4-2210979 |
Correction to eMIMO BFD test cases_r16 |
Huawei, Hisilicon |
R4-2210980 |
Update to UL switching test cases |
Huawei, Hisilicon |
R4-2210981 |
DraftCR on maintaining L1-SINR measurement test cases R16 |
Huawei, Hisilicon |
R4-2210982 |
CR on accuracy requirements for positioning measurement R16 |
Huawei, Hisilicon |
R4-2210983 |
Updates to accuracy requirements for UE positioning measurements in TS 38.133 |
Ericsson |
R4-2211186 |
draft Cat-F CR (R15) to SCell Activation Test Cases |
Qualcomm Incorporated |
R4-2211187 |
draft Cat-F CR (R16) to SCell Activation Test Cases NR-U |
Qualcomm Incorporated |
R4-2211212 |
CR on accuracy requirements for positioning measurement R16 |
Huawei, Hisilicon |
R4-2211236 |
Big CR for TS 38.133 Perf Maintenance Part-1 (Rel-15) |
MCC, Huawei |
R4-2211237 |
Big CR for TS 38.133 Perf Maintenance Part-1 (Rel-16) |
MCC, Huawei |
R4-2211238 |
Big CR for TS 38.133 Perf Maintenance Part-1 (Rel-17) |
MCC, Huawei |
R4-2211239 |
Big CR for TS 38.133 Perf Maintenance Part-2 (Rel-15) |
MCC. Nokia |
R4-2211240 |
Big CR for TS 38.133 Perf Maintenance Part-2 (Rel-16) |
MCC. Nokia |
R4-2211241 |
Big CR for TS 38.133 Perf Maintenance Part-2 (Rel-17) |
MCC. Nokia |
4.1.6.1 |
UE demodulation requirements |
|
R4-2207791 |
CR for mTRP demod requirements applicability (Rel-16) |
Apple |
R4-2207792 |
CR for mTRP demod requirements applicability (Rel-17) |
Apple |
R4-2208532 |
CR on PDSCH requirements for HST-972 and TDLC300-600 |
CMCC |
R4-2208533 |
CR on PDSCH requirements for HST-972 and TDLC300-600 |
CMCC |
R4-2208575 |
Correction CA configuration for PDSCH demodulation |
Rohde & Schwarz |
R4-2208576 |
Correction CA configuration for PDSCH demodulation |
Rohde & Schwarz |
R4-2208578 |
Discussion on scheduling conflicts in UE performance RMCs |
Rohde & Schwarz |
R4-2209851 |
draftCR: Updates to test parameters for NR Rel-16 UE requirements (38.101-4, Rel-16) |
Huawei, HiSilicon |
R4-2209852 |
draftCR: Updates to test parameters for NR Rel-16 UE requirements (38.101-4, Rel-17) |
Huawei, HiSilicon |
R4-2209853 |
draftCR: Modification on test parameters for FR2 SDR test (38.101-4 Rel-15) |
Huawei, HiSilicon |
R4-2209854 |
draftCR: Modification on test parameters for FR2 SDR test (38.101-4 Rel-16) |
Huawei, HiSilicon |
R4-2209855 |
draftCR: Modification on test parameters for FR2 SDR test (38.101-4 Rel-17) |
Huawei, HiSilicon |
R4-2209856 |
draftCR: Modification on test parameters for eMTC test (36.101 Rel-14) |
Huawei, HiSilicon |
R4-2209857 |
draftCR: Modification on test parameters for eMTC test (36.101 Rel-15) |
Huawei, HiSilicon |
R4-2209858 |
draftCR: Modification on test parameters for eMTC test (36.101 Rel-16) |
Huawei, HiSilicon |
R4-2209859 |
draftCR: Modification on test parameters for eMTC test (36.101 Rel-17) |
Huawei, HiSilicon |
R4-2209996 |
Draft CR on Correction in TDD LTE-NR Coexistence Tests |
Qualcomm Incorporated |
R4-2209998 |
Draft CR on Correction in TDD LTE-NR Coexistence Tests |
Qualcomm Incorporated |
R4-2210322 |
Email discussion summary for [103-e][316] Demod_Maintenance_UE |
Moderator (Apple) |
R4-2210519 |
Email discussion summary for [103-e][316] Demod_Maintenance_UE |
Moderator (Apple) |
R4-2210650 |
LS on incorrect PMI reporting |
Apple |
R4-2210893 |
CR for mTRP demod requirements applicability (Rel-16) |
Apple |
R4-2210894 |
Draft CR on Correction in TDD LTE-NR Coexistence Tests |
Qualcomm Incorporated |
R4-2210896 |
draftCR: Updates to test parameters for NR Rel-16 UE requirements (38.101-4, Rel-16) |
Huawei, HiSilicon |
R4-2211204 |
LS on Incorrect PMI Reporting |
Apple |
4.1.6.2 |
CSI requirements |
|
R4-2207651 |
Draft CR to Reporting of Channel Quality Indicator (CQI) for CA |
Anritsu Corporation |
R4-2207652 |
Draft CR to Reporting of Channel Quality Indicator (CQI) for CA |
Anritsu Corporation |
R4-2210895 |
Draft CR to Reporting of Channel Quality Indicator (CQI) for CA |
Anritsu Corporation |
4.1.6.3 |
BS demodulation requirements |
|
R4-2209038 |
[dCR] Maintenance for IAB-MT performance requirement R16 |
ZTE Corporation |
R4-2209039 |
[dCR] Maintenance for IAB-MT performance requirement R17 Cat A |
ZTE Corporation |
R4-2209672 |
Draft CR to TS 38.104: 64QAM BS demodulation FRC description correction, Rel-16 |
Huawei, HiSilicon |
R4-2209673 |
Draft CR to TS 38.104: 64QAM BS demodulation FRC description correction, Rel-17 |
Huawei, HiSilicon |
R4-2210321 |
Email discussion summary for [103-e][315] Demod_Maintenance_BS |
Moderator (ZTE) |
R4-2210518 |
Email discussion summary for [103-e][315] Demod_Maintenance_BS |
Moderator (ZTE) |
R4-2210649 |
Draft CR to TS 38.141-2: 64QAM BS demodulation FRC description correction, Rel-16 |
Huawei, HiSilicon |
R4-2210892 |
Draft CR to TS 38.104: 64QAM BS demodulation FRC description correction, Rel-16 |
Huawei, HiSilicon |
R4-2211315 |
Big CR for TS 38.104 Maintenance Demod part (Rel-16, CAT F) |
MCC, Nokia |
R4-2211316 |
Big CR for TS 38.104 Maintenance Demod part (Rel-17, CAT A) |
MCC, Nokia |
4.1.7 |
NR MIMO OTA test methods (38.827) |
|
R4-2208625 |
draft CR to TR38.827 on UE mechanical mode |
vivo |
R4-2210936 |
draft CR to TR38.827 on UE mechanical mode |
vivo |
R4-2211344 |
Big CR for TR 38.827 maintenance (Rel-16, CAT F) |
Vivo |
5.1.2 |
Introduction of operation in full unlicensed band 5925-7125MHz for NR |
|
R4-2210239 |
Email discussion summary for [103-e][103] NR_6GHz_unlic_full_maintenance |
Moderator (Apple) |
R4-2210439 |
Email discussion summary for [103-e][103] NR_6GHz_unlic_full_maintenance |
Moderator (Apple) |
R4-2210544 |
CR to TR 38.849 on adding NS value for South Korea VLP mode |
Apple, LGE |
5.1.2.1 |
UE RF requirements |
|
R4-2208534 |
CR on NR-U A-MPR for PC5 VLP in South Korea |
LG Electronics, ETRI, Charter Communications Inc., Apple Inc. |
R4-2210703 |
CR on NR-U A-MPR for PC5 VLP in South Korea |
LG Electronics, ETRI, Charter Communications Inc., Apple Inc. |
5.1.3 |
Introduction of 1900 MHz spectrum to 5G NR applicable for Rail Mobile Radio |
|
R4-2208642 |
Revised TR 38.852 version 0.3.0 |
Union Inter. Chemins de Fer |
R4-2208902 |
TP to TR 38.852 - Clarification BS output power |
Ericsson, UIC |
R4-2210319 |
Email discussion summary for [103-e][313] on Rel-17 5G NR applicable for Rail Mobile Radio on 900MHz |
Moderator (Huawei) |
R4-2210516 |
Email discussion summary for [103-e][313] on Rel-17 5G NR applicable for Rail Mobile Radio on 900MHz |
Moderator (Huawei) |
R4-2210644 |
CR to TS 38.104: RMR900 Rx requirements for band n100, Rel-17 |
Huawei, HiSilicon |
R4-2210645 |
CR to TS 37.105: introduction of n100 co-existence requirements, Rel-17 |
Huawei, HiSilicon |
R4-2210646 |
CR to TS 37.145-1: introduction of n100 co-existence requirements, Rel-17 |
Huawei, HiSilicon |
R4-2210647 |
CR to TS 37.145-2: introduction of n100 co-existence requirements, Rel-17 |
Huawei, HiSilicon |
R4-2210882 |
TP to TR 38.852 - Clarification BS output power |
Ericsson, UIC |
R4-2210883 |
Revised TR 38.852 version 0.3.0 |
Union Inter. Chemins de Fer |
R4-2211228 |
Revised TR 38.853 version 0.5.0 |
Union Inter. Chemins de Fer |
5.1.5 |
DC of 5 bands LTE inter-band CA (5DL/1L) and 1 NR band (1DL/1UL) |
|
R4-2208433 |
Summary on new request to Dual Connectivity (DC) of 5 bands LTE inter-band CA (5DL/1UL) and 1 NR band (1DL/1UL) |
Samsung |
5.1.8 |
High power UE (power class 2) for NR FDD band |
|
R4-2210240 |
Email discussion summary for [103-e][104] NR_PC2_UE_FDD_maintenance |
Moderator (China Unicom) |
R4-2210440 |
Email discussion summary for [103-e][104] NR_PC2_UE_FDD_maintenance |
Moderator (China Unicom) |
R4-2211172 |
WF on A-MPR for NS_05 |
Huawei, HiSilicon |
5.1.8.1 |
UE RF requirements |
|
R4-2208685 |
CR to TS38.101-1: Corrections on MSD for PC2 FDD band |
ZTE Corporation,China Unicom |
R4-2209180 |
CR to TS38101-1 Update of PC2 A-MPR for NS_05 |
Huawei, HiSilicon |
R4-2209181 |
Consideration on practical PA implementation for NS_05 A-MPR |
Huawei, HiSilicon |
R4-2210701 |
CR to TS38101-1 Update of PC2 A-MPR for NS_05 |
Huawei, HiSilicon |
R4-2210702 |
CR to TS38.101-1: Corrections on MSD for PC2 FDD band |
ZTE Corporation,China Unicom |
5.1.10 |
Upper 700MHz A Block new E-UTRA band in US |
|
R4-2208646 |
CR to TS 38.101-1: Protection for band 103 from newly introduced CA combinations |
Puloli |
R4-2210716 |
CR to TS 38.101-1: Protection for band 103 from newly introduced CA combinations |
Puloli |
5.2.1 |
UE RF requirements for Transparent Tx Diversity (TxD) for NR |
|
R4-2210241 |
Email discussion summary for [103-e][105] NR_TxD_maintenance |
Moderator (Qualcomm) |
R4-2210441 |
Email discussion summary for [103-e][105] NR_TxD_maintenance |
Moderator (Qualcomm) |
R4-2210545 |
WF on PC1.5 behavior in power class fall back |
Apple |
R4-2210546 |
WF on PC1.5 handling for single port configuration in Rel-16 |
Qualcomm |
5.2.1.1 |
General |
|
R4-2208599 |
Revision of General part of MPR of 38.837 |
vivo |
R4-2208600 |
Big CR for supplementation of 38.837 |
vivo |
5.2.1.2 |
UE RF requirements |
|
R4-2207662 |
Discussion on adding PC1.5 = TxD text |
Qualcomm Incorporated |
R4-2207991 |
Addition of MPR evaluation part to 38.837 |
Skyworks Solutions Inc. |
R4-2208577 |
Update of TxD inband emissions |
Rohde & Schwarz |
R4-2208743 |
Definition of PC1.5 and applicability of extensions of power-class parameters (RRC) |
Ericsson |
R4-2208744 |
Definition of PC1.5 and applicability of extensions of power-class parameters (RRC) |
Ericsson |
R4-2208745 |
Single-port fallback requirement for full-power UL-MIMO modes |
Ericsson |
R4-2208842 |
CR to TS38.101-1 for the corrections on Tx Diversity Requirement |
Samsung |
R4-2209034 |
Draft CR on SRS IL for NR TxD |
ZTE Wistron Telecom AB |
R4-2209308 |
Discussion on TxD signaling and power class fallback |
Apple |
R4-2209309 |
CR on new modifiedMPR-Behavior for power class fallback with Tx Diversity |
Apple |
R4-2209422 |
CR to TR38.837 for TxD SRS IL |
OPPO |
R4-2210704 |
Update of TxD inband emissions |
Rohde & Schwarz |
R4-2210705 |
CR to TS38.101-1 for the corrections on Tx Diversity Requirement |
Samsung |
R4-2210706 |
Draft CR on SRS IL for NR TxD |
ZTE Wistron Telecom AB |
R4-2210707 |
Addition of MPR evaluation part to 38.837 |
Skyworks Solutions Inc. |
R4-2210708 |
Single-port fallback requirement for full-power UL-MIMO modes |
Ericsson |
R4-2211213 |
Addition of MPR evaluation part to 38.837 |
Skyworks Solutions Inc. |
5.2.2 |
Support for Multi-SIM devices for LTE/NR |
|
R4-2210275 |
Email discussion summary for [103-e][203] LTE_NR_MUSIM_maintenance |
Moderator (vivo) |
R4-2210472 |
Email discussion summary for [103-e][203] LTE_NR_MUSIM_maintenance |
Moderator (vivo) |
R4-2210582 |
WF on LTE_NR_MUSIM_maintenance |
vivo |
5.2.2.1 |
RRM core requirements |
|
R4-2209423 |
Clarification on remaining issues for Rel-17 MUSIM |
vivo |
R4-2209447 |
New gap pattern for MUSIM |
Ericsson |
R4-2209448 |
CR on New gap pattern for MUSIM |
Ericsson |
R4-2210986 |
CR on New gap pattern for MUSIM |
Ericsson |
5.3.1 |
BS RF requirements |
|
R4-2208119 |
Draft CR for TS 38.174 R17: correction of the co-existence and co-location tables |
CATT |
R4-2208120 |
Draft CR for TS 38.176-1 R17: correction of the co-existence and co-location tables |
CATT |
R4-2208122 |
Draft CR for TS 38.176-2 R17: correction of the co-existence and co-location test requirements |
CATT |
R4-2208129 |
Draft CR for TS 38.141-2 R17: correction of BS type 1-O co-existence table |
CATT |
R4-2208839 |
CR to 38.141-2: BS FR2 OBUE Cat B requirement table note clarification (6.7.4.5.2) |
Keysight Technologies UK Ltd |
R4-2210695 |
Draft CR for TS 38.174 R17: correction of the co-existence and co-location tables |
CATT |
R4-2210697 |
Draft CR for TS 38.176-2 R17: correction of the co-existence and co-location test requirements |
CATT |
R4-2210698 |
Draft CR for TS 38.141-2 R17: correction of BS type 1-O co-existence table |
CATT |
R4-2210699 |
CR to 38.141-2: BS FR2 OBUE Cat B requirement table note clarification (6.7.4.5.2) |
Keysight Technologies UK Ltd |
5.3.2 |
UE RF requirements |
|
R4-2207665 |
CR 36101-h50 adding fallbacks |
Apple |
R4-2207666 |
CR 38101-1-h50 adding FR1 NR-CA fallbacks |
Apple |
R4-2207667 |
CR 38101-2-h50 adding fallbacks |
Apple |
R4-2207668 |
CR 38101-3-h50 adding FR1+FR2 CA fallbacks |
Apple |
R4-2207669 |
CR 38101-3-h50 adding FR1 EN-DC fallbacks |
Apple |
R4-2207670 |
CR 38101-3-h50 adding EN-DC or NR-DC with FR2 fallbacks |
Apple |
R4-2208290 |
Draft CR for 36.101 Correction to Bands for NB-IoT in the USA |
Dish Network |
R4-2208291 |
Draft CR for 36.101 Correction to Bands for NB-IoT in the USA |
Dish Network |
R4-2208292 |
Draft CR for 36.101 Correction to Bands for NB-IoT in the USA |
Dish Network |
R4-2208293 |
Draft CR for 36.101 Correction to Bands for NB-IoT in the USA |
Dish Network |
R4-2208404 |
Draft CR for 38.101-1- update signalling of maximum duty cycle for FR1 PC1 |
CMCC |
R4-2208405 |
CR for 36.101- add BCS 1 for band8 intra-band contiguous CA |
CMCC |
R4-2208666 |
CR to TS38.101-1[R17] Some Corrections for Transmitter characteristics |
ZTE Corporation |
R4-2208678 |
CR to TS38.101-1: Some corrections for the tables due to introduction of 35MHz_45MHz CBW |
ZTE Corporation, Skyworks Solutions Inc. |
R4-2208746 |
Correction to additional spurious emission requirements for n48 |
Ericsson |
R4-2209033 |
DraftCR for TS 38.101-1 on correction on IL for SRS antenna switching |
ZTE Wistron Telecom AB |
R4-2209037 |
Draft CR for TS 38.307 on Annex B |
ZTE Wistron Telecom AB |
R4-2209054 |
DraftCR for TS 38.101-1 on correction on IL for SRS antenna switching |
ZTE Wistron Telecom AB |
R4-2209109 |
LTE CA corrections R17 |
Nokia |
R4-2209316 |
CR for TS 38.101-3 Rel-17: Corrections on band combinations for UE co-existence |
Apple |
R4-2209317 |
CR for TS 38.101-1 Rel-17: Corrections on band combinations for UE co-existence |
Apple |
R4-2209318 |
CR for TS 36.101 Rel-17: Corrections on band combinations for UE co-existence |
Apple |
R4-2209346 |
Draft CR for 36.101 to clarify the definition about con-current operation (R14) |
Huawei, HiSilicon |
R4-2209347 |
Draft CR for 36.101 to clarify the definition about con-current operation (R15) |
Huawei, HiSilicon |
R4-2209348 |
Draft CR for 36.101 to clarify the definition about con-current operation (R16) |
Huawei, HiSilicon |
R4-2209349 |
Draft CR for 36.101 to clarify the definition about con-current operation (R17) |
Huawei, HiSilicon |
R4-2209354 |
CR for 38.101-1 to change table 7.3.2-1 to clause 7.3.2 for general REFSENS (R17) |
Huawei, HiSilicon |
R4-2210217 |
Correction of MPE Duty Cycle Parameter Name |
Lenovo |
R4-2210227 |
CR to R16 TS38.101-1 on transient period capability |
Skyworks Solutions Inc., Qualcomm Incorporated |
R4-2210229 |
CR to R17 TS38.101-1 on transient period capability |
Skyworks Solutions Inc., Qualcomm Incorporated. |
R4-2210242 |
Email discussion summary for [103-e][106] R17_Maintenance |
Moderator (Ericsson) |
R4-2210442 |
Email discussion summary for [103-e][106] R17_Maintenance |
Moderator (Ericsson) |
R4-2210709 |
CR 36101-h50 adding fallbacks |
Apple |
R4-2210710 |
CR 38101-1-h50 adding FR1 NR-CA fallbacks |
Apple |
R4-2210711 |
CR 38101-3-h50 adding FR1+FR2 CA fallbacks |
Apple |
R4-2210712 |
CR 38101-3-h50 adding FR1 EN-DC fallbacks |
Apple |
R4-2210713 |
CR 38101-3-h50 adding EN-DC or NR-DC with FR2 fallbacks |
Apple |
R4-2210714 |
Draft CR for 36.101 Correction to Bands for NB-IoT in the USA |
Dish Network |
R4-2210715 |
Draft CR for 38.101-1- update signalling of maximum duty cycle for FR1 PC1 |
CMCC |
R4-2210717 |
CR to TS38.101-1[R17] Some Corrections for Transmitter characteristics |
ZTE Corporation |
R4-2210718 |
CR to TS38.101-1: Some corrections for the tables due to introduction of 35MHz_45MHz CBW |
ZTE Corporation, Skyworks Solutions Inc. |
R4-2210719 |
CR for TS 38.101-1 Rel-17: Corrections on band combinations for UE co-existence |
Apple |
R4-2210721 |
CR to R16 TS38.101-1 on transient period capability |
Skyworks Solutions Inc., Qualcomm Incorporated |
R4-2210722 |
CR to R17 TS38.101-1 on transient period capability |
Skyworks Solutions Inc., Qualcomm Incorporated. |
R4-2211185 |
CR 38101-2-h50 adding fallbacks |
Apple |
5.3.3 |
RRM requirements |
|
R4-2207641 |
Correction of Configuration Parameters for Test 1 in Test Case A.7.1.11 |
STMicroelectronics |
R4-2209242 |
Discussion on mapping table for NR TADV |
Huawei, Hisilicon |
R4-2209243 |
CR on mapping table for NR TADV [NRTADV] |
Huawei, Hisilicon |
R4-2209453 |
Remaining issue for Idle mode |
Ericsson |
R4-2209454 |
CR on cell reselection in Idle mode |
Ericsson |
R4-2209455 |
CR on cell selection in Idle mode for NR-U |
Ericsson |
R4-2210122 |
Discussion on number of carriers for NR SA in Rel-17 |
Ericsson |
R4-2210123 |
Draft CR on number of carriers to support for NR SA in Rel-17 |
Ericsson |
R4-2210186 |
On timing advance (TADV) measurement report mapping |
Ericsson |
R4-2210187 |
Timing advance (TADV) measurement report mapping in TS 38.133 |
Ericsson, NTT DOCOMO |
R4-2210274 |
Email discussion summary [103-e][202] Maintenance_R17_RRM |
Moderator (Apple) |
R4-2210471 |
Email discussion summary [103-e][202] Maintenance_R17_RRM |
Moderator (Apple) |
R4-2210984 |
CR on mapping table for NR TADV [NRTADV] |
Huawei, Hisilicon |
R4-2210985 |
Correction of Configuration Parameters for Test 1 in Test Case A.7.1.11 |
STMicroelectronics |
R4-2211167 |
LS on timing advance (TADV) report mapping for NR UL E-CID positioning |
Ericsson |
R4-2211169 |
WF about the cell selection initiation for Idle mode |
Ericsson |
5.3.5.1 |
Incorrect PMI reporting |
|
R4-2207793 |
Discussion on incorrect PMI reporting |
Apple |
R4-2209690 |
Discussion on the incorrect PMI reporting |
Ericsson |
R4-2209796 |
Discussion on PMI requirements for inter-cell interference scenario |
MediaTek inc. |
R4-2209893 |
Discussion on incorrect PMI reporting with inter-cell interference |
Huawei, HiSilicon |
5.3.5.2 |
Canada band n77 |
|
R4-2208747 |
Extension of operation in the n77 frequency range in Canada |
Ericsson |
R4-2208867 |
Discussion on band n77 issue |
Xiaomi |
R4-2209108 |
n77 Canada |
Nokia |
R4-2209638 |
Extended frequency range 3650-3980 MHz in Canada band n77 |
Mediatek India Technology Pvt. |
R4-2210816 |
Extension of operation in the n77 frequency range in Canada |
Ericsson |
6 |
LS response to ITU |
|
R4-2210320 |
Email discussion summary for [103-e][314] LS_Response_ITU-R |
Moderator (Ericsson) |
R4-2210517 |
Email discussion summary for [103-e][314] LS_Response_ITU-R |
Moderator (Ericsson) |
R4-2210648 |
WF on LS response to WP5D on Generic unwanted emission (IMT-2020) |
Ericsson, Nokia, Qualcomm, ZTE, Huawei |
6.1 |
Generic unwanted emission (IMT-2020) |
|
R4-2207889 |
LS on unwanted emissions for IMT-2020 |
Ericsson |
R4-2207920 |
Input on LS response to ITU-R on Generic unwanted emission (IMT-2020) |
Nokia, Nokia Shanghai Bell |
R4-2208086 |
Work plan on LS response to ITU-R on Generic unwanted emission (IMT-2020) |
Qualcomm CDMA Technologies |
R4-2209591 |
Input on LS response to ITU-R on Generic unwanted emission (IMT-2020) |
ZTE Corporation |
R4-2209645 |
Inputs to the ITU-R LS response on generic unwanted emission for (IMT-2020): Receiver spurious emissions |
Huawei, HiSilicon |
6.2 |
Test methods for OTA total radiated power |
|
R4-2207888 |
LS on Test methods for over-the-air TRP field measurements of unwanted emissions from IMT radio equipment utilizing active antennas |
Ericsson, Qualcomm, Huawei, Nokia |
R4-2210889 |
LS on Test methods for over-the-air TRP field measurements of unwanted emissions from IMT radio equipment utilizing active antennas |
Ericsson, Qualcomm, Huawei, Nokia |
7 |
Rel-17 feature list |
|
R4-2207785 |
Further discussion on R17 feature list |
Apple |
R4-2207955 |
A new Rel-17 per-FR MG capability based on Per BC |
Qualcomm Incorporated |
R4-2208051 |
Discussion on Rel-17 RAN4 UE feature list |
Intel Corporation |
R4-2208304 |
Regarding UE feature and capability for 1024QAM |
MediaTek inc. |
R4-2208768 |
Discussion on Rel-17 feature list |
Huawei, HiSilicon |
R4-2209258 |
On Rel.17 RAN4 Features |
Qualcomm Incorporated |
R4-2209375 |
R17 Per band Per BC power class capability |
OPPO |
R4-2210200 |
Rel-17 feature group for increasing MOP of CA and DC |
Qualcomm Incorporated |
R4-2210271 |
Email discussion summary for [103-e][136] R17_feature_list |
Moderator (CMCC) |
R4-2210436 |
Rel-17 RAN4 UE feature list for NR |
CMCC |
R4-2210437 |
LS on Rel-17 RAN4 UE feature list for NR |
CMCC |
R4-2210468 |
Email discussion summary for [103-e][136] R17_feature_list |
Moderator (CMCC) |
R4-2211189 |
Rel-17 RAN4 UE feature list for NR |
CMCC |
R4-2211190 |
LS on Rel-17 RAN4 UE feature list for NR |
CMCC |
8 |
Rel-17 spectrum related WIs for NR |
|
R4-2208893 |
CR to TS 38.133 - Introduction of licensed 6GHz band n104 |
Ericsson |
8.1 |
Introduction of 6GHz NR licensed bands |
|
R4-2210249 |
Email discussion summary for [103-e][114] NR_6 GHz_licensed |
Moderator (Huawei, HiSilicon) |
R4-2210449 |
Email discussion summary for [103-e][114] NR_6 GHz_licensed |
Moderator (Huawei, HiSilicon) |
R4-2210553 |
Reply LS on request information on progress and timeline relating to 6 GHz NR licensed bands |
Huawei |
8.1.2 |
System parameters |
|
R4-2208196 |
System parameters for 6GHz licensed band |
CATT |
R4-2208407 |
Discussion on system parameters for 6GHz licensed spectrum |
CMCC |
R4-2208547 |
System parameters for 6GHz NR licensed band |
Huawei, HiSilicon, China Unicom |
R4-2208655 |
System Parameters of n104 |
Nokia, Nokia Shanghai Bell |
R4-2208860 |
Discussion the remaining issues on system parameters for 6G license band |
Xiaomi |
R4-2208890 |
Licensed 6GHz: General aspects - system parameters |
Ericsson |
R4-2209579 |
Discussion on system parameters for 6425-7125MHz |
ZTE Corporation |
R4-2210195 |
System parameters for the 6 GHz licensed band |
Qualcomm Incorporated |
8.1.3 |
UE RF requirements |
|
R4-2207664 |
On UE Rx requirements for the licensed operation in the upper 6GHz frequency range |
Apple |
R4-2208197 |
UE RF requirements for 6GHz licensed band |
CATT |
R4-2208340 |
Discussion on UE REFSENS for 6GHz licensed band |
Mediatek India Technology Pvt. |
R4-2208408 |
Discussion on UE requirements for 6GHz licensed spectrum |
CMCC |
R4-2208548 |
Remaining issues on UE TX RF requirements |
Huawei, HiSilicon, China Unicom |
R4-2208549 |
Remaining issues on UE RX RF requirements |
Huawei, HiSilicon, China Unicom |
R4-2208861 |
REFSENs for 6G license band |
Xiaomi |
R4-2208891 |
Licensed 6GHz: Remaining UE RF open issues |
Ericsson |
R4-2209580 |
Discussion on UE RF requirements for 6425-7125MHz |
ZTE Corporation |
R4-2210196 |
UE RF requirements for the 6 GHz licensed band |
Qualcomm Incorporated |
R4-2210197 |
Introduction of NR licensed band 6425 – 7125 MHz |
Qualcomm Incorporated |
R4-2210742 |
Introduction of NR licensed band 6425 – 7125 MHz |
Qualcomm Incorporated |
R4-2211224 |
Introduction of NR licensed band 6425 – 7125 MHz |
Qualcomm Incorporated, Skyworks Solutions, Inc. |
8.1.4 |
BS RF requirements |
|
R4-2207921 |
Proposals on BS RF requirements for introduction of 6GHz licensed band |
Nokia, Nokia Shanghai Bell |
R4-2207922 |
CR to TR 38.176-1 on introduction of 6GHz licensed band |
Nokia, Nokia Shanghai Bell |
R4-2208242 |
Remaining issue for BS RF requriement in 6GHz band |
CATT |
R4-2208243 |
Introducing 6GHz licensed operation into 38.141-1 |
CATT |
R4-2208244 |
Introducing 6GHz licensed operation into 37.105 |
CATT |
R4-2208245 |
Introducing 6GHz licensed operation into 38.174 |
CATT |
R4-2208409 |
Discussion on BS requirements for 6GHz licensed spectrum |
CMCC |
R4-2208550 |
Remaining issues on BS RF requirements |
Huawei, HiSilicon, China Unicom |
R4-2208551 |
Measurement uncertainty for 6 to 7.125GHz |
Huawei, HiSilicon |
R4-2208552 |
CR on introduction of 6GHz licensed band for 37.145-1 |
Huawei, HiSilicon |
R4-2208553 |
CR on introduction of 6GHz licensed band for 37.145-2 |
Huawei, HiSilicon |
R4-2208892 |
Licensed 6GHz: Remaining BS RF open issues |
Ericsson |
R4-2208894 |
CR to TS 38.141-2 - Introduction of licensed 6GHz band n104 |
Ericsson |
R4-2208895 |
CR to TS 38.176-2 - Introduction of licensed 6GHz band n104 |
Ericsson |
R4-2209537 |
CR to 37.104 on introduction of n104 co-existence requirements |
Nokia, Nokia Shanghai Bell |
R4-2209538 |
CR to 37.141 on introduction of n104 co-existence requirements |
Nokia, Nokia Shanghai Bell |
R4-2209581 |
Discussion on BS RF requirements for 6425-7125MHz |
ZTE Corporation |
R4-2209582 |
CR to TS38.104 the introduction of 6425-7125MHz |
ZTE Corporation |
R4-2209583 |
CR to TS36.104 the introduction of coexistence requirements of licensed band 6425-7125MHz |
ZTE Corporation |
R4-2209584 |
CR to TS36.141 the introduction of coexistence requirements of licensed band 6425-7125MHz |
ZTE Corporation |
R4-2210739 |
Introducing 6GHz licensed operation into 37.105 |
CATT |
R4-2210740 |
CR to TS38.104 the introduction of 6425-7125MHz |
ZTE Corporation |
R4-2210741 |
CR to TS36.141 the introduction of coexistence requirements of licensed band 6425-7125MHz |
ZTE Corporation |
8.1.5 |
Others |
|
R4-2210276 |
Email discussion summary for [103-e][204] Spectrum_RRM |
Moderator (Ericsson) |
R4-2210473 |
Email discussion summary for [103-e][204] Spectrum_RRM |
Moderator (Ericsson) |
R4-2210987 |
CR to TS 38.133 - Introduction of licensed 6GHz band n104 |
Ericsson |
R4-2210989 |
CR on adding B48 for M1/M2/NB1/NB2 |
Ericsson |
8.2 |
Introduction of 900 MHz spectrum to 5G NR applicable for Rail Mobile Radio |
|
R4-2208654 |
Revised TR 38.853 version 0.4.0 |
Union Inter. Chemins de Fer |
R4-2209270 |
TP 900MHz RMR band – conclusion- TR 38.853 |
Union Inter. Chemins de Fer |
R4-2209585 |
Discussion on sync raster design for railway 900MHz |
ZTE Corporation |
R4-2210884 |
TP 900MHz RMR band – conclusion- TR 38.853 |
Union Inter. Chemins de Fer |
8.2.1 |
UE RF requirements |
|
R4-2208281 |
Synchronisation raster for bandwidth less than 5MHz |
Huawei Tech.(UK) Co.. Ltd |
R4-2209721 |
Synchronization raster design for n100 |
Nokia, Nokia Shanghai Bell |
8.2.2 |
BS RF requirements |
|
R4-2208896 |
RMR 900MHz: Remaining BS RF open issues |
Ericsson |
R4-2208897 |
CR to TS 38.104 - Tx requirements: RMR 900MHz band introduction |
Ericsson |
R4-2208898 |
CR to TS 38.141-2: RMR 900MHz band introduction |
Ericsson |
R4-2208899 |
CR to TS 36.104: RMR 900MHz band introduction |
Ericsson |
R4-2208900 |
CR to TS 36.141: RMR 900MHz band introduction |
Ericsson |
R4-2209530 |
CR to 37.104 on introduction of n100 co-existence requirements |
Nokia, Nokia Shanghai Bell |
R4-2209531 |
CR to 37.141 on introduction of n100 co-existence requirements |
Nokia, Nokia Shanghai Bell |
R4-2209532 |
CR to 38.104 on introduction of n100 (system parameters) |
Nokia, Nokia Shanghai Bell |
R4-2209533 |
CR to 38.141-1 on introduction of n100 requirements |
Nokia, Nokia Shanghai Bell |
R4-2209674 |
Draft CR to TS 38.104: RMR900 Rx requirements for band n100, Rel-17 |
Huawei, HiSilicon |
R4-2210885 |
CR to TS 38.104 - Tx requirements: RMR 900MHz band introduction |
Ericsson |
R4-2210886 |
CR to 37.141 on introduction of n100 co-existence requirements |
Nokia, Nokia Shanghai Bell |
R4-2210887 |
CR to 38.104 on introduction of n100 (system parameters) |
Nokia, Nokia Shanghai Bell |
R4-2210888 |
CR to 38.141-1 on introduction of n100 requirements |
Nokia, Nokia Shanghai Bell |
8.2.3 |
RRM requirements |
|
R4-2208901 |
CR to TS 38.133: RMR 900MHz band introduction |
Ericsson |
R4-2209675 |
Draft CR to TS 38.133: implementation of RMR900 band n100, Rel-17 |
Huawei, HiSilicon |
R4-2210988 |
CR to TS 38.133: RMR 900MHz band introduction |
Ericsson |
8.3 |
Issues arising from basket WIs but not subject to block approval |
|
R4-2210250 |
Email summary for [103-e][115] NR_Baskets_Part_1 |
Moderator (Skyworks Solutions Inc.) |
R4-2210450 |
Email summary for [103-e][115] NR_Baskets_Part_1 |
Moderator (Skyworks Solutions Inc.) |
R4-2210554 |
TP on TR 37.717-11-11 Update on the MSD value of DC_(n)3 |
Huawei, MediaTek, Qualcomm, Skyworks |
R4-2210555 |
WF on CA_n18-n28 second cross-band isolation MSD test point |
Skyworks Solutions Inc. |
R4-2210556 |
WF on guidelines on valid CBW for higher band combination configurations depending on fallbacks |
ZTE, Skyworks Solutions Inc. |
R4-2210557 |
WF on criteria for triple beat MSD analysis |
Qualcomm, Skyworks Solutions Inc. |
R4-2211128 |
Draft TP to TR on DC_1A_(n)3AA |
Huawei |
8.3.1 |
UE RF requirements |
|
R4-2207716 |
TP for TR 37.717-21-11 Addition of DC_12-30_n5 |
AT&T |
R4-2207717 |
TP for TR 37.717-21-11 Addition of DC_14-30_n5 |
AT&T |
R4-2207718 |
TP for TR 37.717-21-11 Addition of DC_14-66_n5 |
AT&T |
R4-2207988 |
Additional criteria for triple beat issue detection |
Skyworks Solutions Inc. |
R4-2207989 |
Completion of inter-band band combinations with intra-band ULCA in UL configuration |
Skyworks Solutions Inc. |
R4-2207993 |
Draft CR to TS 38.101-1 V17.5.0 on intra-band ULCA UL configurations |
Skyworks Solutions Inc. |
R4-2208002 |
DC_(n)3AA MSD |
Qualcomm Incorporated |
R4-2208003 |
DC_28_n40-n41 MSD |
Qualcomm Incorporated |
R4-2208004 |
DC_(n)7AA MSD |
Qualcomm Incorporated |
R4-2208707 |
TP for TR38.717-03-02_CA_n28A-n40A-n41A |
ZTE Corporation |
R4-2209252 |
second test point for CA_n18-n28 MSD |
Skyworks Solutions Inc. |
R4-2209273 |
Draft CR for 38.101-3 to remove incorrect UL configuration for DC_1_n28-n75 and DC_3_n28-n75 and add back DC_3C-20A_n7A-n28A |
Huawei, HiSilicon, DT |
R4-2209274 |
Draft CR for 38.101-3 to add UL configuration DC_3C_n28A and DC_3C_n78A for DC_3C-20A_n28A-n78A |
Huawei, HiSilicon, DT |
R4-2209560 |
TP for TR 37 717-11-11 to include CA_n7(AA) |
Ericsson, Telstra |
R4-2209568 |
draft CR 38.101-3 to add missing configurations |
Ericsson, BT plc |
R4-2209936 |
TP to TR 38.717-02-01 Addition of CA_n7-n40 |
Nokia |
R4-2209942 |
TP to TR 38.717-03-02 Addition of CA_n1-n7-n40 |
Nokia |
R4-2209944 |
TP to TR 38.717-03-02 Addition of CA_n7-n8-n40 |
Nokia |
R4-2210108 |
Draft CR to TS 38.101-3 V17.5.0 on intra-band ULCA UL configurations |
Skyworks Solutions Inc. |
R4-2210153 |
Draft CR to TS 38.101-1 V17.5.0 on removing CBW in NRCA band combination that are missing in lower fallbacks |
Skyworks Solutions Inc. |
R4-2210233 |
Single Uplink MSD for DC_(n)3AA |
Skyworks Solutions Inc. |
R4-2210743 |
TP for TR 37 717-11-11 to include CA_n7(AA) |
Ericsson, Telstra |
R4-2210744 |
Draft CR to TS 38.101-3 V17.5.0 on intra-band ULCA UL configurations |
Skyworks Solutions Inc. |
R4-2210745 |
Draft CR to TS 38.101-1 V17.5.0 on intra-band ULCA UL configurations |
Skyworks Solutions Inc. |
R4-2211214 |
Draft CR to TS 38.101-3 V17.5.0 on intra-band ULCA UL configurations |
Skyworks Solutions Inc. |
8.4 |
NR intra band Carrier Aggregation for xCC DL/yCC UL including contiguous and non-contiguous spectrum (x>=y) |
|
R4-2210251 |
Email discussion summary [103-e][116] NR_Baskets_Part_2 |
Moderator (Nokia) |
8.4.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2209542 |
Revised WID NR Intra-band Rel-17 |
Ericsson |
R4-2209546 |
big CR 38.101-1 new combinations Rel-17 NR Intra-band |
Ericsson |
R4-2209547 |
big CR 38.101-2 new combinations Rel-17 NR Intra-band |
Ericsson |
R4-2209551 |
TR 38.717-01-01 v0.9.0 Rel-17 NR Intra-band |
Ericsson |
8.4.2 |
UE RF requirements for FR1 |
|
R4-2209111 |
DraftCR 38.101-1: Addition of CA_n25(2A) and CA_n25(3A) BCS4 |
Nokia, T-Mobile USA |
R4-2209112 |
DraftCR 38.101-1: CA_n41(3A) BCS4 and CA_n41(4A) BCS0 and 4 |
Nokia, T-Mobile USA |
R4-2209113 |
DraftCR 38.101-1: CA_n41(A-C) BCS4 and CA_n41(2A-C) BCS0 and 4 |
Nokia, T-Mobile USA |
R4-2209114 |
DraftCR 38.101-1: CA_n66(2A) BCS4 |
Nokia, T-Mobile USA |
R4-2209115 |
DraftCR 38.101-1: CA_n71(2A) BCS4 |
Nokia, T-Mobile USA |
R4-2209116 |
DraftCR 38.101-1:CA_n71B BCS4 |
Nokia, T-Mobile USA |
R4-2209117 |
DraftCR 38.101-1: CA_n77(2A) BCS4 |
Nokia, T-Mobile USA |
R4-2210358 |
DraftCR 38.101-1: Addition of CA_n25(2A) and CA_n25(3A) BCS4 |
Nokia, T-Mobile USA |
R4-2210359 |
DraftCR 38.101-1: CA_n41(3A) BCS4 and CA_n41(4A) BCS0 and 4 |
Nokia, T-Mobile USA |
R4-2210360 |
DraftCR 38.101-1: CA_n41(A-C) BCS4 and CA_n41(2A-C) BCS0 and 4 |
Nokia, T-Mobile USA |
R4-2210361 |
DraftCR 38.101-1: CA_n66(2A) BCS4 |
Nokia, T-Mobile USA |
R4-2210362 |
DraftCR 38.101-1: CA_n71(2A) BCS4 |
Nokia, T-Mobile USA |
R4-2210363 |
DraftCR 38.101-1:CA_n71B BCS4 |
Nokia, T-Mobile USA |
R4-2210364 |
DraftCR 38.101-1: CA_n77(2A) BCS4 |
Nokia, T-Mobile USA |
8.5 |
NR inter-band Carrier Aggregation/Dual Connectivity for 2 bands DL with x bands UL (x=1, 2) |
|
R4-2210252 |
Email discussion summary [103-e][117] NR_Baskets_Part_3 |
Moderator (Nokia) |
8.5.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2208708 |
Revised WID on Rel-17 NR Inter-band Carrier Aggregation/Dual Connectivity for 2 bands DL with x bands UL (x=1,2) |
ZTE Corporation |
R4-2208709 |
Big CR to reflect the completed NR inter band CA DC combinations for 2 bands DL with up to 2 bands UL into TS 38.101-1 |
ZTE Corporation |
R4-2208710 |
Big CR to reflect the completed NR inter band CA DC combinations for 2 bands DL with up to 2 bands UL into TS 38.101-2 |
ZTE Corporation |
R4-2208711 |
Big CR to reflect the completed NR inter band CA DC combinations for 2 bands DL with up to 2 bands UL into TS 38.101-3 |
ZTE Corporation |
R4-2209035 |
Draft TR 38.717-02-01 v0.9.0 |
ZTE Wistron Telecom AB |
8.5.2 |
NR inter band CA requirements without any FR2 band(s) |
|
R4-2207744 |
Draft CR for 38.101-1 to introduce CA_n3A-n41B,CA_n28A-n41B and CA_n41B-n77A |
KDDI Corporation |
R4-2207828 |
Draft CR for TS 38.101-1: Support of BCS2 in CA_n41-n79 |
SoftBank Corp. |
R4-2207829 |
Draft CR for TS 38.101-1: Support of n77(3A) in CA_n77-n79 |
SoftBank Corp. |
R4-2207986 |
TP for TR 38.717-02-01: Updates to CA_n24-n77 RefSens requirements clause |
Ligado Networks |
R4-2208438 |
TP for TR 38.717-02-01 CA_n5-n40 |
Samsung, Spark |
R4-2208689 |
Draft CR to TS38.101-1: CA_n34A-n79C |
ZTE Corporation |
R4-2208690 |
TP for TR 38.717-02-01: CA_n28A-n34A |
ZTE Corporation |
R4-2208691 |
TP for TR 38.717-02-01: CA_n28A-n39A |
ZTE Corporation |
R4-2208692 |
TP for TR 38.717-02-01: CA_n34A-n41A/C |
ZTE Corporation |
R4-2209119 |
DraftCR 38.101-1: CA_n25-n66 configurations |
Nokia, T-Mobile USA |
R4-2209120 |
DraftCR 38.101-1: CA_n25-n71 configurations |
Nokia, T-Mobile USA |
R4-2209121 |
DraftCR 38.101-1: CA_n25-n77 configurations |
Nokia, T-Mobile USA |
R4-2209122 |
DraftCR 38.101-1: CA_n41-n66 configurations |
Nokia, T-Mobile USA |
R4-2209123 |
DraftCR 38.101-1: CA_n41-n71 configurations |
Nokia, T-Mobile USA |
R4-2209124 |
DraftCR 38.101-1: CA_n41-n77 configurations |
Nokia, T-Mobile USA |
R4-2209125 |
DraftCR 38.101-1: CA_n66-n71 configurations |
Nokia, T-Mobile USA |
R4-2209126 |
DraftCR 38.101-1: CA_n66-n77 configurations |
Nokia, T-Mobile USA |
R4-2209127 |
DraftCR 38.101-1: CA_n71-n77 configurations |
Nokia, T-Mobile USA |
R4-2209275 |
Draft CR for 38.101-1 to add configuration CA_n3B-n79C |
Huawei, HiSilicon |
R4-2209283 |
TP for 38.717-02-01 CA_n28A-n79C with UL_n79C |
Huawei, HiSilicon |
R4-2209284 |
TP for 38.717-02-01 CA_n3A-n79C with UL_n79C |
Huawei, HiSilicon |
R4-2209285 |
TP for 38.717-02-01 CA_n3A-n78C with UL_n78C |
Huawei, HiSilicon |
R4-2209286 |
TP for 38.717-02-01 CA_n1A-n78C with UL_n78C |
Huawei, HiSilicon |
R4-2209287 |
Updated TP for 38.717-02-01 CA_n8A-n77A |
Huawei, HiSilicon, Softbank |
R4-2209927 |
TP to TR 38.717-02-01 Addition of CA_n8-n38 |
Nokia, Telefonica |
R4-2209928 |
TP to TR 38.717-02-01 Addition of CA_n20-n40 |
Nokia, Telefonica |
R4-2209929 |
TP to TR 38.717-02-01 Addition of CA_n38-n40 |
Nokia, Telefonica |
R4-2209932 |
draftCR 38.101-1 Addition of CA_n41A-n77C |
Nokia |
R4-2209933 |
draftCR 38.101-1 Addition of CA_n41A-n78C |
Nokia |
R4-2209934 |
TP to TR 38.717-02-01 Addition of CA_n40-n77 |
Nokia |
R4-2209935 |
draftCR 38.101-1 Addition of CA_n40A-n78C |
Nokia |
R4-2209966 |
draftCR 38.101-3 Addition of DC_1A_n7A-n782A |
Nokia, BT |
R4-2210378 |
Draft CR for 38.101-1 to introduce CA_n3A-n41B,CA_n28A-n41B and CA_n41B-n77A |
KDDI Corporation |
R4-2210379 |
TP for TR 38.717-02-01: Updates to CA_n24-n77 RefSens requirements clause |
Ligado Networks |
R4-2210380 |
TP for TR 38.717-02-01 CA_n5-n40 |
Samsung, Spark |
R4-2210381 |
TP for TR 38.717-02-01: CA_n28A-n34A |
ZTE Corporation |
R4-2210382 |
TP for TR 38.717-02-01: CA_n28A-n39A |
ZTE Corporation |
R4-2210383 |
TP for TR 38.717-02-01: CA_n34A-n41A/C |
ZTE Corporation |
R4-2210384 |
DraftCR 38.101-1: CA_n25-n66 configurations |
Nokia, T-Mobile USA |
R4-2210385 |
DraftCR 38.101-1: CA_n25-n71 configurations |
Nokia, T-Mobile USA |
R4-2210386 |
DraftCR 38.101-1: CA_n25-n77 configurations |
Nokia, T-Mobile USA |
R4-2210387 |
DraftCR 38.101-1: CA_n41-n66 configurations |
Nokia, T-Mobile USA |
R4-2210388 |
DraftCR 38.101-1: CA_n41-n71 configurations |
Nokia, T-Mobile USA |
R4-2210389 |
DraftCR 38.101-1: CA_n41-n77 configurations |
Nokia, T-Mobile USA |
R4-2210390 |
DraftCR 38.101-1: CA_n66-n71 configurations |
Nokia, T-Mobile USA |
R4-2210391 |
DraftCR 38.101-1: CA_n66-n77 configurations |
Nokia, T-Mobile USA |
R4-2210392 |
DraftCR 38.101-1: CA_n71-n77 configurations |
Nokia, T-Mobile USA |
R4-2210393 |
TP for 38.717-02-01 CA_n3A-n78C with UL_n78C |
Huawei, HiSilicon |
R4-2210394 |
Updated TP for 38.717-02-01 CA_n8A-n77A |
Huawei, HiSilicon, Softbank |
R4-2210395 |
TP to TR 38.717-02-01 Addition of CA_n8-n38 |
Nokia, Telefonica |
R4-2210396 |
TP to TR 38.717-02-01 Addition of CA_n20-n40 |
Nokia, Telefonica |
R4-2210397 |
TP to TR 38.717-02-01 Addition of CA_n38-n40 |
Nokia, Telefonica |
R4-2210398 |
TP to TR 38.717-02-01 Addition of CA_n40-n77 |
Nokia |
R4-2210399 |
draftCR 38.101-1 Addition of CA_n40A-n78C |
Nokia |
R4-2210748 |
TP to TR 38.717-02-01 Addition of CA_n7-n40 |
Nokia |
8.5.3 |
NR inter band CA requirements with at least one FR2 band |
|
R4-2207703 |
draft CR 38.101-3 to add new NR CA 2DL/1UL combinations |
Charter Communications, Inc |
R4-2207830 |
Draft CR for TS 38.101-3: Support of n77(2A) and n258D/G/H/I in CA_n77-n258 |
SoftBank Corp. |
R4-2207831 |
Draft CR for TS 38.101-3: Addition of UL configurations in CA_n79-n258 |
SoftBank Corp. |
R4-2207934 |
DraftCR 38.101-3: Addition of FR1+FR2 combos |
Verizon, ZTE, Samsung |
R4-2208339 |
draft CR for CA_n8-n257, DC_n8-n257 |
CHTTL |
R4-2209118 |
DraftCR 38.101-1: CA_n25-n41 configurations |
Nokia, T-Mobile USA |
R4-2209276 |
Draft CR for 38.101-3 to add configuration CA_n3A-n257JkLM |
Huawei, HiSilicon |
R4-2209277 |
Draft CR for 38.101-3 to add configuration CA_n3B-n258AGHIJkLM and CA_n3(2A)-n258AGHIJkLM |
Huawei, HiSilicon |
R4-2209278 |
Draft CR for 38.101-3 to add configuration CA_n7A-n257AGHIJkLM |
Huawei, HiSilicon |
R4-2209279 |
Draft CR for 38.101-3 to add configuration CA_n79A-n257JkLM |
Huawei, HiSilicon |
R4-2209280 |
Draft CR for 38.101-3 to add configuration CA_n79A-n258M |
Huawei, HiSilicon |
R4-2209281 |
Draft CR for 38.101-3 to add configuration CA_n38A-n257AGHIJkLM |
Huawei, HiSilicon |
R4-2209282 |
Draft CR for 38.101-3 to add configuration CA_n38A-n258AGHIJkLM |
Huawei, HiSilicon |
R4-2209574 |
draft CR 38.101-2 on correction in 2DL NR CA configuration table |
Ericsson |
R4-2209575 |
draft CR 38.101-3 on corrections in 2DL NR CA configuration table |
Ericsson |
R4-2209618 |
Draft CR for TS 38.101-3 to add configurations CA_n3A-n257(2A) and DC_n3A-n257(2A) |
ZTE Corporation |
R4-2209619 |
Draft CR for TS 38.101-3 to add configurations CA_n3A-n258(2A) and DC_n3A-n258(2A) |
ZTE Corporation |
R4-2209620 |
Draft CR for TS 38.101-3 to add configurations CA_n78A-n257(2A) and DC_n78A-n257(2A) |
ZTE Corporation |
R4-2209621 |
Draft CR for TS 38.101-3 to add configurations CA_n78A-n258(2A) and DC_n78A-n258(2A) |
ZTE Corporation |
R4-2210051 |
Draft CR for 38.101-3: Consolidation of DC_n41-n66-n260 |
T-Mobile USA Inc. |
R4-2210377 |
DraftCR 38.101-1: CA_n25-n41 configurations |
Nokia, T-Mobile USA |
R4-2210400 |
draft CR 38.101-3 to add new NR CA 2DL/1UL combinations |
Charter Communications, Inc |
R4-2210401 |
draft CR for CA_n8-n257, DC_n8-n257 |
CHTTL |
R4-2210402 |
Draft CR for 38.101-3: Consolidation of DC_n41-n66-n260 |
T-Mobile USA Inc. |
8.6.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2208238 |
TR 38.717-03-01 on Rel-17 NR inter-band Carrier Aggregation (CA) for 3 Down Link (DL) / 1 Up Link (UL) v.0.8.0 |
CATT |
R4-2208239 |
Revised WID on Rel-17 NR inter-band CA of 3DL bands and 1UL band |
CATT |
R4-2208240 |
CR on Introducing NR inter-band CA for 3DL Bands and 1UL band for 38.101-1 |
CATT |
R4-2208241 |
CR on Introducing NR inter-band CA for 3DL Bands and 1UL band for 38.101-3 |
CATT |
8.6.2 |
UE RF requirements |
|
R4-2207745 |
Draft CR for 38.101-1 to introduce new configurations for NR inter-band CA 3 bands DL with 1 band UL |
KDDI Corporation |
R4-2207834 |
Draft CR for TS 38.101-3: Support of n77 intra-band non-contiguous CA in CA_n28-n77-n257 and CA_n41-n77-n257 |
SoftBank Corp. |
R4-2207847 |
TP for TR 38.717-03-01: NR CA_n77-n79-n258 |
SoftBank Corp. |
R4-2208306 |
TP for TR 38.717-03-01: support of CA_n8-n78-n257 |
CHTTL |
R4-2208434 |
Draft CR for 38.101-1 to introduce new configurations for NR inter-band CA 3 bands DL with 1 band UL |
Samsung, KDDI |
R4-2208439 |
TP for TR 38.717-03-01 CA_n5-n40-n78 |
Samsung, Spark |
R4-2208699 |
TP for TR38.717-03-01_CA_n3A-n8A-n41A |
ZTE Corporation |
R4-2208700 |
TP for TR38.717-03-01_CA_n3A-n8A-n79A |
ZTE Corporation |
R4-2208701 |
TP for TR38.717-03-01_CA_n8A-n39A-n79A |
ZTE Corporation |
R4-2208702 |
TP for TR38.717-03-01_CA_n28A-n39A-n40A |
ZTE Corporation |
R4-2208703 |
TP for TR38.717-03-01_CA_n28A-n39A-n41 |
ZTE Corporation |
R4-2208704 |
TP for TR38.717-03-01_CA_n28A-n39A-n79A |
ZTE Corporation |
R4-2209288 |
TP for 38.717-03-01 CA_n1A-n28A-n38A |
Huawei, HiSilicon |
R4-2209289 |
Draft CR for 38.101-1 to add configuration CA_n1A-n28A-n78A_BCS2 |
Huawei, HiSilicon |
R4-2209290 |
TP for 38.717-03-01 CA_n1A-n38A-n78A |
Huawei, HiSilicon |
R4-2209291 |
TP for 38.717-03-01 CA_n28A-n38A-n78A |
Huawei, HiSilicon |
R4-2209292 |
Draft CR for 38.101-1 to add configuration CA_n1A-n3B-n7A CA_n1A-n3(2A)-n7A CA_n1(2A)-n3A-n7A CA_n1(2A)-n3B-n7A and CA_n1(2A)-n3(2A)-n7A |
Huawei, HiSilicon |
R4-2209293 |
TP for 38.717-03-01 CA_n1A-n7A-n79A CA_n1(2A)-n7A-n79A CA_n1A-n7A-n79C and CA_n1(2A)-n7A-n79C |
Huawei, HiSilicon |
R4-2209930 |
TP to TR 38.717-03-01 Addition of CA_n3-n38-n40 |
Nokia, Telefonica |
R4-2209931 |
TP to TR 38.717-03-01 Addition of CA_n8-n38-n40 |
Nokia, Telefonica |
R4-2209937 |
TP to TR 38.717-03-01 Addition of CA_n1-n7-n40 |
Nokia |
R4-2209938 |
TP to TR 38.717-03-01 Addition of CA_n1-n8-n40 |
Nokia |
R4-2209939 |
TP to TR 38.717-03-01 Addition of CA_n7-n8-n40 |
Nokia |
R4-2209940 |
TP to TR 38.717-03-01 Addition of CA_n8-n40-n78 |
Nokia |
8.7.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2209544 |
Revised WID 4DL/1UL NR CA Rel-17 |
Ericsson |
R4-2209549 |
big CR 38.101-1 new combinations NR CA Inter-band 4DL/1UL |
Ericsson |
R4-2209553 |
TR 38.717-04-01 v0.9.0 Rel-17 NR CA Inter-band 4DL/1UL |
Ericsson |
R4-2209569 |
draft CR converting 38.101-1 4DL configuration table into new table format |
Ericsson |
8.7.2 |
UE RF requirements |
|
R4-2207837 |
Draft CR for TS 38.101-3: Support of n77(3A) in CA_n3-n28-n77-n257 |
SoftBank Corp. |
R4-2207838 |
Draft CR for TS 38.101-3: Support of n257H/I in CA_n28-n41-n77-n257 |
SoftBank Corp. |
R4-2207849 |
TP for TR 38.717-04-01: CA_n1-n3-n41-n257 |
SoftBank Corp. |
R4-2207850 |
TP for TR 38.717-04-01: CA_n1-n28-n41-n257 |
SoftBank Corp. |
R4-2207851 |
TP for TR 38.717-04-01: CA_n1-n41-n77-n257 |
SoftBank Corp. |
R4-2208312 |
TP for TR 38.717-04-01: support of CA_n1-n8-n78-n257 |
CHTTL |
R4-2208436 |
Draft CR for 38.101-1 to introduce new configurations for NR inter-band CA 4 bands DL with 1 band UL |
Samsung, KDDI |
R4-2209947 |
TP to TR 38.717-04-01 Addition of CA_n1-n7-n8-n40 |
Nokia |
R4-2209948 |
TP to TR 38.717-04-01 Addition of CA_n1-n7-n8-n78 |
Nokia |
R4-2209949 |
TP to TR 38.717-04-01 Addition of CA_n1-n7-n40-n78 |
Nokia |
R4-2209950 |
TP to TR 38.717-04-01 Addition of CA_n1-n8-n40-n78 |
Nokia |
R4-2209951 |
TP to TR 38.717-04-01 Addition of CA_n7-n8-n40-n78 |
Nokia |
R4-2209977 |
TP for 38.717-04-01 to introduce CA_n2A-n12A-n30A-n77A |
Nokia, AT&T |
R4-2209978 |
TP for 38.717-04-01 to introduce CA_n2A-n12A-n66A-n77A |
Nokia, AT&T |
R4-2209979 |
TP for 38.717-04-01 to introduce CA_n2A-n29A-n30A-n77A |
Nokia, AT&T |
R4-2209980 |
TP for 38.717-04-01 to introduce CA_n2A-n29A-n66A-n77A |
Nokia, AT&T |
R4-2209981 |
TP for 38.717-04-01 to introduce CA_n12A-n30A-n66A-n77A |
Nokia, AT&T |
R4-2209982 |
TP for 38.717-04-01 to introduce CA_n29A-n30A-n66A-n77A |
Nokia, AT&T |
8.8.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2209036 |
Draft TR 38.717-03-02 v0.9.0 |
ZTE Wistron Telecom AB |
R4-2209635 |
Revised WID on Rel-17 NR Inter-band Carrier AggregationDual Connectivity for 3 bands DL with 2 bands UL, ZTE Corporation |
ZTE Corporation |
R4-2209636 |
Big CR to reflect the completed NR inter band CA DC combinations for 3 bands DL with 2 bands UL into TS 38.101-1 |
ZTE Corporation |
R4-2209637 |
Big CR to reflect the completed NR inter band CA DC combinations for 3 bands DL with 2 bands UL into TS 38.101-3 |
ZTE Corporation |
8.8.2 |
UE RF requirements |
|
R4-2207746 |
Draft CR for 38.101-1 to introduce new configurations for NR inter-band CA 3 bands DL with 2 bands UL |
KDDI Corporation |
R4-2207833 |
Draft CR for TS 38.101-3: Support of n77(3A) in CA_n3-n77-n257 and CA_n28-n77-n257 |
SoftBank Corp. |
R4-2207845 |
TP for TR 38.717-03-02: CA_n3-n41-n257 |
SoftBank Corp. |
R4-2207846 |
TP for TR 38.717-03-02: CA_n28-n41-n257 |
SoftBank Corp. |
R4-2207860 |
TP update for TR 38.717-03-02: CA_n3-n28-n41 |
SoftBank Corp., ZTE Corporation |
R4-2207928 |
DraftCR 38.101-3 Addition of Missing DL and UL configurations for NR CA and NR-DC Combinations |
AT&T |
R4-2207929 |
TP for TR 38.717-03-02: CA/DC_n5-n66-n261 |
Verizon, Samsung |
R4-2207930 |
TP for TR 38.717-03-02: CA/DC_n2-n66-n261 |
Verizon, Samsung |
R4-2207931 |
TP for TR 38.717-03-02: CA/DC_n2-n5-n261 |
Verizon, Samsung |
R4-2208435 |
Draft CR for 38.101-1 to introduce new configurations for NR inter-band CA 3 bands DL with 2 bands UL |
Samsung, KDDI |
R4-2208440 |
TP for TR 38.717-03-02 CA_n5-n40-n78 |
Samsung, Spark |
R4-2208563 |
DraftCR for 38.101-3: BCS1 for CA_n66-n77-n260 |
Huawei, HiSilicon, Bell Mobility, Telus |
R4-2208688 |
Draft CR to TS38.101-1: CA_n28A-n41C-n79A |
ZTE Corporation |
R4-2208705 |
TP for TR38.717-03-02_CA_n1A-n8A-n78A |
ZTE Corporation, CHTTL |
R4-2208706 |
TP for TR38.717-03-02_CA_n28A-n39A-n41 |
ZTE Corporation |
R4-2209565 |
draft CR 38.101-3 to add new NR CA 3DL 2UL combinations |
Ericsson, AT&T |
R4-2209566 |
draft CR 38.101-3 to add new NR DC 3DL 2UL combinations |
Ericsson, AT&T |
R4-2209572 |
draft CR 38.101-1 on corrections in 3DL NR CA configuration table |
Ericsson |
R4-2209576 |
draft CR 38.101-3 on corrections in 3DL NR CA configuration table |
Ericsson |
R4-2209941 |
TP to TR 38.717-03-02 Addition of CA_n1-n7-n8 |
Nokia |
R4-2209943 |
TP to TR 38.717-03-02 Addition of CA_n1-n8-n40 |
Nokia |
R4-2209945 |
TP to TR 38.717-03-02 Addition of CA_n7-n8-n78 |
Nokia |
R4-2209946 |
TP to TR 38.717-03-02 Addition of CA_n8-n40-n78 |
Nokia |
R4-2209964 |
draftCR 38.101-1 Addition of DC_n1A-n7A-n78A |
Nokia, BT |
R4-2209965 |
draftCR 38.101-1 Addition of DC_n7-n46-n78 |
Nokia, BT |
R4-2209971 |
draftCR to add configurations for CA_n2-n5-n66 to 38.101-1 |
Nokia, AT&T |
R4-2209973 |
draftCR to add configurations for CA_n2-n14-n66 to 38.101-1 |
Nokia, AT&T |
R4-2209974 |
draftCR to add configurations for CA_n2-n30-n66 to 38.101-1 |
Nokia, AT&T |
R4-2209975 |
draftCR to add configurations for CA_n5-n30-n66 to 38.101-1 |
Nokia, AT&T |
R4-2209976 |
draftCR to add configurations for CA_n14-n30-n66 to 38.101-1 |
Nokia, AT&T |
R4-2210041 |
DraftCR 38.101-3 Addition of Missing UL configurations for NR CA and NR-DC Combinations |
AT&T |
R4-2210070 |
draftCR 38.101-1 to add CA_n25A-n41A-n66A, CA_n25A-n41A-n66(2A), CA_n25A-n41C-n66A, CA_n25A-n41(2A)-n66A, CA_n25(2A)-n41A-n66A |
Ericsson, T-Mobile US |
R4-2210071 |
draftCR 38.101-1 to add CA_n25A-n41A-n71A, CA_n25A-n41A-n71B, CA_n25A-n41A-n71(2A), CA_n25A-n41C-n71A, CA_n25A-n41(2A)-n71A, CA_n25(2A)-n41A-n71A |
Ericsson, T-Mobile US |
R4-2210072 |
draftCR 38.101-1 to add CA_n25A-n41A-n77A,CA_n25A-n41A-n77(2A), CA_n25A-n41C-n77A, CA_n25A-n41(2A)-n77A, CA_n25(2A)-n41A-n77A, CA_n25A-n41(2A)-n77(2A), CA_n25A-n41C-n77(2A) |
Ericsson, T-Mobile US |
R4-2210073 |
draftCR 38.101-1 to add CA_n25A-n66A-n71A, CA_n25A-n66A-n71B, CA_n25A-n66A-n71(2A), CA_n25A-n66(2A)-n71A, CA_n25(2A)-n66A-n71A |
Ericsson, T-Mobile US |
R4-2210074 |
draftCR 38.101-1 to add CA_n25A-n66A-n77A, CA_n25A-n66A-n77(2A), CA_n25A-n66(2A)-n77A, CA_n25(2A)-n66A-n77A |
Ericsson, T-Mobile US |
R4-2210075 |
draftCR 38.101-1 to add CA_n25A-n71A-n77A, CA_n25A-n71B-n77A, CA_n25A-n71(2A)-n77A, CA_n25(2A)-n71A-n77A |
Ericsson, T-Mobile US |
R4-2210076 |
draftCR 38.101-1 to add CA_n41A-n66A-n71A, CA_n41A-n66A-n71B, CA_n41A-n66A-n71(2A),CA_n41A-n66(2A)-n71A, CA_n41C-n66A-n71A, CA_n41(2A)-n66A-n71A |
Ericsson, T-Mobile US |
R4-2210077 |
draftCR 38.101-1 to add CA_n41A-n66A-n77A, CA_n41A-n66A-n77(2A),CA_n41A-n66(2A)-n77A, CA_n41A-n66(2A)-n77(2A), CA_n41C-n66A-n77A, CA_n41(2A)-n66A-n77A, CA_n41(2A)-n66A-n77(2A), CA_n41C-n66A-n77(2A) |
Ericsson, T-Mobile US |
R4-2210078 |
draftCR 38.101-1 to add CA_n41A-n71A-n77A, CA_n41A-n71A-n77(2A), CA_n41A-n71B-n77A, CA_n41A-n71(2A)-n77A, CA_n41C-n71A-n77A, CA_n41(2A)-n71A-n77A, CA_n41C-n71A-n77(2A), CA_n41(2A)-n71A-n77(2A) |
Ericsson, T-Mobile US |
R4-2210079 |
draftCR 38.101-1 to add CA_n66A-n71A-n77A, CA_n66A-n71A-n77(2A), CA_n66A-n71B-n77A, CA_n66A-n71(2A)-n77A, CA_n66(2A)-n71A-n77A |
Ericsson, T-Mobile US |
R4-2210403 |
TP to TR 38.717-03-02 Addition of CA_n8-n40-n78 |
Nokia |
R4-2210404 |
Draft CR for 38.101-1 to introduce new configurations for NR inter-band CA 3 bands DL with 2 bands UL |
KDDI Corporation |
R4-2210405 |
TP for TR 38.717-03-02: CA_n3-n41-n257 |
SoftBank Corp. |
R4-2210406 |
TP for TR 38.717-03-02: CA_n28-n41-n257 |
SoftBank Corp. |
R4-2210407 |
DraftCR for 38.101-3: BCS1 for CA_n66-n77-n260 |
Huawei, HiSilicon, Bell Mobility, Telus |
R4-2210408 |
draft CR 38.101-3 to add new NR CA 3DL 2UL combinations |
Ericsson, AT&T |
R4-2210409 |
draftCR 38.101-1 to add CA_n25A-n41A-n66A, CA_n25A-n41A-n66(2A), CA_n25A-n41C-n66A, CA_n25A-n41(2A)-n66A, CA_n25(2A)-n41A-n66A |
Ericsson, T-Mobile US |
R4-2210410 |
draftCR 38.101-1 to add CA_n25A-n41A-n71A, CA_n25A-n41A-n71B, CA_n25A-n41A-n71(2A), CA_n25A-n41C-n71A, CA_n25A-n41(2A)-n71A, CA_n25(2A)-n41A-n71A |
Ericsson, T-Mobile US |
R4-2210411 |
draftCR 38.101-1 to add CA_n25A-n41A-n77A,CA_n25A-n41A-n77(2A), CA_n25A-n41C-n77A, CA_n25A-n41(2A)-n77A, CA_n25(2A)-n41A-n77A, CA_n25A-n41(2A)-n77(2A), CA_n25A-n41C-n77(2A) |
Ericsson, T-Mobile US |
R4-2210412 |
draftCR 38.101-1 to add CA_n25A-n66A-n71A, CA_n25A-n66A-n71B, CA_n25A-n66A-n71(2A), CA_n25A-n66(2A)-n71A, CA_n25(2A)-n66A-n71A |
Ericsson, T-Mobile US |
R4-2210413 |
draftCR 38.101-1 to add CA_n25A-n66A-n77A, CA_n25A-n66A-n77(2A), CA_n25A-n66(2A)-n77A, CA_n25(2A)-n66A-n77A |
Ericsson, T-Mobile US |
R4-2210414 |
draftCR 38.101-1 to add CA_n25A-n71A-n77A, CA_n25A-n71B-n77A, CA_n25A-n71(2A)-n77A, CA_n25(2A)-n71A-n77A |
Ericsson, T-Mobile US |
R4-2210415 |
draftCR 38.101-1 to add CA_n41A-n66A-n71A, CA_n41A-n66A-n71B, CA_n41A-n66A-n71(2A),CA_n41A-n66(2A)-n71A, CA_n41C-n66A-n71A, CA_n41(2A)-n66A-n71A |
Ericsson, T-Mobile US |
R4-2210416 |
draftCR 38.101-1 to add CA_n41A-n66A-n77A, CA_n41A-n66A-n77(2A),CA_n41A-n66(2A)-n77A, CA_n41A-n66(2A)-n77(2A), CA_n41C-n66A-n77A, CA_n41(2A)-n66A-n77A, CA_n41(2A)-n66A-n77(2A), CA_n41C-n66A-n77(2A) |
Ericsson, T-Mobile US |
R4-2210417 |
draftCR 38.101-1 to add CA_n41A-n71A-n77A, CA_n41A-n71A-n77(2A), CA_n41A-n71B-n77A, CA_n41A-n71(2A)-n77A, CA_n41C-n71A-n77A, CA_n41(2A)-n71A-n77A, CA_n41C-n71A-n77(2A), CA_n41(2A)-n71A-n77(2A) |
Ericsson, T-Mobile US |
R4-2210418 |
draftCR 38.101-1 to add CA_n66A-n71A-n77A, CA_n66A-n71A-n77(2A), CA_n66A-n71B-n77A, CA_n66A-n71(2A)-n77A, CA_n66(2A)-n71A-n77A |
Ericsson, T-Mobile US |
8.9.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2208428 |
TR 38.717-04-02 update version 0.9.0 |
Samsung |
R4-2208430 |
Big CR on introduction of completed NR CA/DC combs with 4DL/2UL within FR1 |
Samsung |
R4-2208431 |
Big CR on introduction of completed NR CA/DC combs with 4DL/2UL including FR2 |
Samsung |
R4-2208432 |
Revised WID on NR CA/DC with 4DL/2UL |
Samsung |
8.9.2 |
UE RF requirements |
|
R4-2207840 |
Draft CR for TS 38.101-1: Support of DC_n1-n3-n28-n77/79, DC_n1-n3/28-n77-n79, DC_n3-n28-n41-n77 and DC_n3-n28-77-n79 |
SoftBank Corp. |
R4-2208437 |
Draft CR for 38.101-1 to introduce new configurations for NR inter-band CA 4 bands DL with 2 bands UL |
Samsung, KDDI |
R4-2208473 |
Draft CR for 38.101-3 to change 4DL configuration table into new format |
Samsung |
R4-2209128 |
DraftCR 38.101-1: CA_n25-n41-n66-n71 configurations |
Nokia, T-Mobile USA |
R4-2209129 |
DraftCR 38.101-1: CA_n25-n41-n66-n77 configurations |
Nokia, T-Mobile USA |
R4-2209130 |
DraftCR 38.101-1: CA_n25-n41-n71-n77 configurations |
Nokia, T-Mobile USA |
R4-2209131 |
DraftCR 38.101-1: CA_n25-n66-n71-n77 configurations |
Nokia, T-Mobile USA |
R4-2209132 |
DraftCR 38.101-1: CA_n41-n66-n71-n77 configurations |
Nokia, T-Mobile USA |
R4-2209952 |
TP to TR 38.717-04-02 Addition of CA_n1-n7-n8-n40 |
Nokia |
R4-2209953 |
TP to TR 38.717-04-02 Addition of CA_n1-n7-n8-n78 |
Nokia |
R4-2209954 |
TP to TR 38.717-04-02 Addition of CA_n1-n7-n40-n78 |
Nokia |
R4-2209955 |
TP to TR 38.717-04-02 Addition of CA_n1-n8-n40-n78 |
Nokia |
R4-2209956 |
TP to TR 38.717-04-02 Addition of CA_n7-n8-n40-n78 |
Nokia |
R4-2209970 |
draftCR to add configurations for CA_n2-n5-n30-n66 to 38.101-1 |
Nokia, AT&T |
R4-2209972 |
draftCR to add configurations for CA_n2-n14-n30-n66 to 38.101-1 |
Nokia, AT&T |
R4-2209983 |
TP for 38.717-04-02 to introduce CA_n2A-n12A-n30A-n77A |
Nokia, AT&T |
R4-2209984 |
TP for 38.717-04-02 to introduce CA_n2A-n12A-n66A-n77A |
Nokia, AT&T |
R4-2209985 |
TP for 38.717-04-02 to introduce CA_n2A-n29A-n30A-n77A |
Nokia, AT&T |
R4-2209986 |
TP for 38.717-04-02 to introduce CA_n2A-n29A-n66A-n77A |
Nokia, AT&T |
R4-2209987 |
TP for 38.717-04-02 to introduce CA_n12A-n30A-n66A-n77A |
Nokia, AT&T |
R4-2209988 |
TP for 38.717-04-02 to introduce CA_n29A-n30A-n66A-n77A |
Nokia, AT&T |
R4-2210419 |
TP to TR 38.717-04-02 Addition of CA_n1-n7-n8-n40 |
Nokia |
R4-2210420 |
TP to TR 38.717-04-02 Addition of CA_n1-n7-n8-n78 |
Nokia |
R4-2210421 |
TP to TR 38.717-04-02 Addition of CA_n1-n7-n40-n78 |
Nokia |
R4-2210422 |
TP to TR 38.717-04-02 Addition of CA_n1-n8-n40-n78 |
Nokia |
R4-2210423 |
TP to TR 38.717-04-02 Addition of CA_n7-n8-n40-n78 |
Nokia |
R4-2210424 |
DraftCR 38.101-1: CA_n25-n41-n66-n71 configurations |
Nokia, T-Mobile USA |
R4-2210425 |
DraftCR 38.101-1: CA_n25-n41-n66-n77 configurations |
Nokia, T-Mobile USA |
R4-2210426 |
DraftCR 38.101-1: CA_n25-n41-n71-n77 configurations |
Nokia, T-Mobile USA |
R4-2210427 |
DraftCR 38.101-1: CA_n25-n66-n71-n77 configurations |
Nokia, T-Mobile USA |
R4-2210428 |
DraftCR 38.101-1: CA_n41-n66-n71-n77 configurations |
Nokia, T-Mobile USA |
8.10.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2209263 |
Revised WID on NR inter-band CA for 5 bands DL with x bands UL (x=1, 2) |
Huawei, HiSilicon |
R4-2209264 |
TR 38.717-05-01 v1.0.0 |
Huawei, HiSilicon |
R4-2209265 |
Big CR on Introduction of completed 5 bands inter-band CA into TS 38.101-1 |
Huawei, HiSilicon |
R4-2209266 |
Big CR on Introduction of completed 5 bands inter-band CA into TS 38.101-3 |
Huawei, HiSilicon |
8.10.2 |
UE RF requirements |
|
R4-2209573 |
draft CR 38.101-1 on corrections in 5DL NR CA configuration table |
Ericsson |
8.11.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2207892 |
Big CR for Rel-17 Dual Connectivity (DC) of 1 LTE band (1DL/1UL) and 1 NR band (1DL/1UL) |
CHTTL |
R4-2207893 |
TR 37.717-11-11 v1.2.0 Rel-17 Dual Connectivity (DC) of 1 LTE band (1DL/1UL) and 1 NR band (1DL/1UL) |
CHTTL |
R4-2207903 |
Revised WID for Rel-17 Dual Connectivity (DC) of 1 LTE band (1DL/1UL) and 1 NR band (1DL/1UL) |
CHTTL |
R4-2208284 |
CR for release independent of Rel.17 NE-DC FR1 and FR2 combinations |
CHTTL, CMCC, SGS Wireless, Samsung |
R4-2209567 |
draft CR 38.101-3 to add DC_1_n7 configuration |
Ericsson, BT plc |
8.11.2 |
EN-DC requirements without FR2 band |
|
R4-2207727 |
DraftCR 38.101-3 Addition of 1 Band LTE and 1 Band NR EN-DC Combinations |
AT&T |
R4-2207859 |
TP update for TR 37.717-11-11: DC_41_n1 |
SoftBank Corp. |
R4-2209570 |
TP for TR 37.717-11-11 to correct DC_2_n25 |
Ericsson |
R4-2209926 |
TP for 37.717-11-11 to introduce DC_71_n77 |
Nokia, US Cellular |
R4-2210357 |
TP for TR 37.717-11-11 for DC_48_n2 |
Verizon |
R4-2210365 |
TP update for TR 37.717-11-11: DC_41_n1 |
SoftBank Corp. |
R4-2210366 |
TP for 37.717-11-11 to introduce DC_71_n77 |
Nokia, US Cellular |
8.11.3 |
EN-DC requirements with FR2 band |
|
R4-2207832 |
Draft CR for TS 38.101-3: Support of UL DC_28A_n257D in DC_28_n257 |
SoftBank Corp. |
R4-2209561 |
draft CR 38.101-3 to add DC_14_n258 |
Ericsson, AT&T |
R4-2209562 |
draft CR 38.101-3 to add DC_30_n258 |
Ericsson, AT&T |
R4-2209622 |
Draft CR for TS 38.101-3 to add EN-DC configuration DC_1A_n257(2A) |
ZTE Corporation |
R4-2209623 |
Draft CR for TS 38.101-3 to add EN-DC configuration DC_1A_n258(2A) |
ZTE Corporation |
R4-2209624 |
Draft CR for TS 38.101-3 to add EN-DC configuration DC_7A_n257(2A) |
ZTE Corporation |
R4-2209625 |
Draft CR for TS 38.101-3 to add EN-DC configuration DC_7A_n258(2A) |
ZTE Corporation |
R4-2210069 |
draft CR 38101-3 to add DC_26A_n258A-M |
Ericsson, Telstra |
8.12.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2208558 |
TR 37.717-21-11 V0.9.0 for DC of 2 LTE band and 1 NR band |
Huawei, HiSilicon |
R4-2208559 |
CR on introduction of completed DC of 2 bands LTE and 1 band NR from RAN4#103-e into TS 38.101-3 |
Huawei, HiSilicon |
R4-2208560 |
Rel-17 WID: Dual Connectivity (DC) of 2 bands LTE inter-band CA (2DL/1UL) and 1 NR band (1DL/1UL) |
Huawei, HiSilicon |
8.12.2 |
EN-DC requirements without FR2 band |
|
R4-2207715 |
TP for TR 37.717-21-11 Addition of DC_2-14_n5 |
AT&T |
R4-2207728 |
DraftCR 38.101-3 Addition of 2 Bands LTE and 1 Band NR EN-DC Combinations |
AT&T |
R4-2207765 |
TP for TR 37.717-21-11: DC_1-20_n7 |
VODAFONE Group Plc |
R4-2207835 |
Draft CR for TS 38.101-3: Correction of DC_5-7_n77 and DC_5-7_n78 |
SoftBank Corp. |
R4-2207932 |
TP for TR 37.717-21-11: DC_48-66_n2 |
Verizon, Samsung |
R4-2207933 |
TP for TR 37.717-21-11: DC_2-48_n2 |
Verizon, Samsung |
R4-2208561 |
draft CR to 38.101-3: corrections on EN-DC configurations |
Huawei, HiSilicon |
R4-2209020 |
TP for TR 37.717-21-11: DC_32A-38A_n28A |
Huawei, HiSilicon |
R4-2209170 |
TP for TR 37.717-21-11 DC_3A-38A_n78A and DC_3C-38A_n78A |
Huawei, HiSilicon |
R4-2209171 |
TP for TR 37.717-21-11 DC_8A-32A_n28A |
Huawei, HiSilicon |
R4-2209272 |
Draft CR for 38.101-3 to correct the editorial error for DC_2A-2A-12A_n78A |
Huawei, HiSilicon |
R4-2209571 |
TP for TR 37.717-21-11 to include DC_2-7_n25 (resubmission of R4-2205702) |
Ericsson |
R4-2209633 |
TP for TR 37.717-21-11_DC_1A-38A_n7A |
ZTE Corporation |
R4-2209634 |
TP for TR 37.717-21-11_DC_3A-38A_n7A |
ZTE Corporation |
R4-2209962 |
TP to TR 37.717-21-11 Addition of DC_40A-42A_n77A |
Nokia, NBN |
R4-2209963 |
TP to TR 37.717-21-11 Addition of DC_40A-42A_n78A |
Nokia, NBN |
R4-2209993 |
TP for TR 37.717-21-11: DC_n77A_1A-3A, DC_n77(2A)_1A-3A |
Huawei Technologies France |
R4-2210367 |
Draft CR for TS 38.101-3: Correction of DC_5-7_n77 and DC_5-7_n78 |
SoftBank Corp. |
R4-2210368 |
TP for TR 37.717-21-11: DC_2-48_n2 |
Verizon, Samsung |
R4-2210369 |
draft CR to 38.101-3: corrections on EN-DC configurations |
Huawei, HiSilicon |
R4-2210370 |
TP for TR 37.717-21-11 DC_3A-38A_n78A and DC_3C-38A_n78A |
Huawei, HiSilicon |
R4-2210371 |
TP for TR 37.717-21-11 to include DC_2-7_n25 (resubmission of R4-2205702) |
Ericsson |
R4-2210372 |
TP to TR 37.717-21-11 Addition of DC_40A-42A_n77A |
Nokia, NBN |
R4-2210373 |
TP to TR 37.717-21-11 Addition of DC_40A-42A_n78A |
Nokia, NBN |
R4-2210747 |
TP for TR 37.717-21-11 Addition of DC_14-66_n5 |
AT&T |
8.12.3 |
EN-DC requirements with FR2 band |
|
R4-2210066 |
draft CR 38101-3 to add DC_1A-26A_n258A-M |
Ericsson, Telstra |
R4-2210067 |
draft CR 38101-3 to add DC_3A-26A_n258A-M |
Ericsson, Telstra |
R4-2210068 |
draft CR 38101-3 to add DC_7A-26A_n258A-M |
Ericsson, Telstra |
8.13.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2209543 |
Revised WID LTE 3DL and one NR band Rel-17 |
Ericsson |
R4-2209548 |
big CR 38.101-3 new combinations LTE 3DL and one NR band |
Ericsson |
R4-2209552 |
TR 37.717-31-11 v0.9.0 Rel-17 DC combinations LTE 3DL and one NR band |
Ericsson |
8.13.2 |
EN-DC requirements without FR2 band |
|
R4-2207719 |
TP for TR 37.717-31-11 Addition of DC_2-30-(n)5 |
AT&T |
R4-2207720 |
TP for TR 37.717-31-11 Addition of DC_30-66-(n)5 |
AT&T |
R4-2207729 |
DraftCR 38.101-3 Addition of 3 Bands LTE and 1 Band NR EN-DC Combinations |
AT&T |
R4-2207940 |
TP for TR 37.717-31-11: DC_2-13-66_n2 |
Verizon, Samsung |
R4-2209021 |
TP for TR 37.717-31-11: DC_3A-32A-38A_n28A and DC_3C-32A-38A_n28A |
Huawei, HiSilicon |
R4-2209172 |
TP for TR 37.717-31-11 DC_3A-8A-32A_n28A and DC_3C-8A-32A_n28A |
Huawei, HiSilicon |
R4-2210374 |
TP for TR 37.717-31-11: DC_3A-32A-38A_n28A and DC_3C-32A-38A_n28A |
Huawei, HiSilicon |
R4-2210375 |
TP for TR 37.717-31-11 DC_3A-8A-32A_n28A and DC_3C-8A-32A_n28A |
Huawei, HiSilicon |
8.13.3 |
EN-DC requirements with FR2 band |
|
R4-2209563 |
draft CR 38.101-3 to add new configurations |
Ericsson, AT&T |
8.14.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2209919 |
Revised Rel-17 WID on DC of 4 bands LTE inter-band CA (4DL1UL) and 1 NR band (1DL1UL) |
Nokia, Nokia Shanghai Bell |
R4-2209920 |
TR 37.717-41-11-110 |
Nokia, Nokia Shanghai Bell |
R4-2209921 |
Big CR to introduce new combinations of LTE 4band + NR 1band for TS 38.101-3 |
Nokia, Nokia Shanghai Bell |
8.14.2 |
EN-DC requirements without FR2 band |
|
R4-2207721 |
TP for TR 37.717-41-11 Addition of DC_2-30-66-(n)5 |
AT&T |
R4-2207841 |
Draft CR for TS 38.101-3: Support of n77(3A) in DC_1-3-8-11_n77 |
SoftBank Corp. |
R4-2210376 |
TP for TR 37.717-41-11 Addition of DC_2-30-66-(n)5 |
AT&T |
8.14.3 |
EN-DC requirements with FR2 band |
|
R4-2209564 |
draft CR 38.101-3 to add new configurations |
Ericsson, AT&T |
8.15.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2207632 |
TR 37.717-11-21 v0.9.0 TR update: LTE(xDL/1UL)+ NR(2DL/1UL) DC in Rel-17 |
LG Electronics Deutschland |
R4-2207633 |
Revised WID on Rel-17 Dual Connectivity (DC) of x bands (x=1,2,3,4) LTE inter-band CA (xDL/1UL) and 2 bands NR inter-band CA (2DL/1UL) |
LG Electronics Deutschland |
R4-2207634 |
Introduction CR on new NR DC LTE(xDL/1UL)+ NR(2DL/1UL) band combinations in Rel-17 |
LG Electronics Deutschland |
R4-2207645 |
Introduction CR on new NR DC LTE(xDL/1UL)+ NR(2DL/1UL) band combinations in Rel-17 |
LG Electronics Deutschland |
8.15.2 |
EN-DC requirements including NR inter CA without FR2 band |
|
R4-2207839 |
Draft CR for TS 38.101-3: Support of n77(2A) in DC_1-8_n77-n79 |
SoftBank Corp. |
R4-2207842 |
Draft CR for TS 38.101-3: Correction of Rib table for DC_11_n1-n77 and DC_8-11_n77-n79 |
SoftBank Corp. |
R4-2207848 |
TP for TR 37.717-11-21: EN-DC_41_n1-n3 |
SoftBank Corp. |
R4-2207852 |
TP for TR 37.717-11-21: EN-DC_8-11_n1-n77 |
SoftBank Corp. |
R4-2207853 |
TP for TR 37.717-11-21: EN-DC_8-41_n1-n3 |
SoftBank Corp. |
R4-2207854 |
TP for TR 37.717-11-21: EN-DC_1-8-11_n3-n79 |
SoftBank Corp. |
R4-2207855 |
TP for TR 37.717-11-21: EN-DC_1-8-11_n77-n79 |
SoftBank Corp. |
R4-2207909 |
TP for TR 37.717-11-21: DC_1_n3-n75 |
VODAFONE Group Plc |
R4-2207910 |
TP for TR 37.717-11-21: DC_20_n7-n78 |
VODAFONE Group Plc |
R4-2207987 |
TP for TR 37.717-11-21: DC_1-20_n7-n78 |
VODAFONE Group Plc |
R4-2208441 |
TP for TR 38.717-11-21 DC_3_n5-n40 |
Samsung, Spark |
R4-2208696 |
TP for TR 37.717-11-21: DC_3A-8A_n40A-n79 |
ZTE Corporation |
R4-2208838 |
TP for TR 37.717-11-21: DC_1A_n8A-n77A, DC_1A_n8A-n77(2A) |
Huawei Technologies France |
R4-2209084 |
TP for TR 37.717-11-21: DC_n8A-n77A_1A, DC_n8A-n77(2A)_1A |
Huawei Technologies France |
R4-2209632 |
TP for TR 37.717-11-21_DC_38A_n7A-n78A |
ZTE Corporation |
R4-2209967 |
draftCR 38.101-3 Addition of DC_1A-3C_n7A-n78A |
Nokia, BT |
R4-2209968 |
draftCR 38.101-3 Addition of DC_3C_n782A UL config |
Nokia, BT |
R4-2209969 |
draftCR 38.101-3 Correction to DC_3C_n7A-n782A |
Nokia, BT |
R4-2209989 |
TP for TR 37.717-11-21: DC_n77A-n257A/G/H/I/J/K/L/M_1A-3A, DC_n77(2A)-n257A/G/H/I/J/K/L/M_1A-3A |
Huawei Technologies France |
R4-2210038 |
TP for TR 37.717-11-21: DC_n8A-n77A_1A, DC_n8A-n77(2A)_1A |
Huawei Technologies France |
R4-2210043 |
TP for TR 37.717-11-21: DC_1A_n8A-n77A, DC_1A_n8A-n77(2A) |
Huawei Technologies France |
R4-2210429 |
TP for TR 37.717-11-21: DC_20_n7-n78 |
VODAFONE Group Plc |
R4-2210430 |
TP for TR 38.717-11-21 DC_3_n5-n40 |
Samsung, Spark |
R4-2210749 |
Draft CR for 38.101-3 to remove incorrect UL configuration for DC_1_n28-n75 and DC_3_n28-n75 and add back DC_3C-20A_n7A-n28A |
Huawei, HiSilicon, DT |
R4-2210750 |
Draft CR for 38.101-3 to add UL configuration DC_3C_n28A and DC_3C_n78A for DC_3C-20A_n28A-n78A |
Huawei, HiSilicon, DT |
R4-2210751 |
draft CR 38.101-3 to add missing configurations |
Ericsson, BT plc |
8.15.3 |
EN-DC requirements including NR inter CA with FR2 band |
|
R4-2207836 |
Draft CR for TS 38.101-3: Support of UL DC_28A_n257D in DC_28_n77-n257 |
SoftBank Corp. |
R4-2208697 |
TP for 37.717-11-21: DC_8A_n79A-n258A |
ZTE Corporation |
R4-2208841 |
TP for TR 37.717-11-21: DC_n77A-n257A/G/H/I/J/K/L/M_1A, DC_n77(2A)-n257A/G/H/I/J/K/L/M_1A |
Huawei Technologies France |
R4-2208877 |
TP for TR 37.717-11-21: DC_n77A-n257A/G/H/I/J/K/L/M_3A, DC_n77(2A)-n257A/G/H/I/J/K/L/M_3A |
Huawei Technologies France |
R4-2209083 |
TP for TR 37.717-11-21: DC_n8A-n77A_1A, DC_n8A-n77(2A)_1A |
Huawei Technologies France |
R4-2209577 |
draft CR 38.101-3 on corrections in EN-DC tables |
Ericsson |
R4-2209957 |
draftCR to add DC_40_n77-n257 to 38.101-3 |
Nokia, NBN |
R4-2209958 |
draftCR to add DC_40-42_n77-n257 to 38.101-3 |
Nokia, NBN |
R4-2209959 |
draftCR to add DC_40-42_n78-n257 to 38.101-3 |
Nokia, NBN |
R4-2209960 |
draftCR to add DC_42_n77-n257 to 38.101-3 |
Nokia, NBN |
R4-2209961 |
draftCR to add DC_42_n78-n257 to 38.101-3 |
Nokia, NBN |
R4-2210037 |
TP for TR 37.717-11-21 DC_n77A-n257A_3A variants DC_n77(2A)-n257A_3A variants |
Huawei Technologies France |
R4-2210058 |
TP for TR 37.717-11-21: DC_n77A-n257A/G/H/I/J/K/L/M_1A, DC_n77(2A)-n257A/G/H/I/J/K/L/M_1A |
Huawei Technologies France |
8.16.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2208712 |
Revised WID on Rel-17 Dual Connectivity (DC) x bands (x=1,2) LTE inter-band CA (xDL/xUL) and y bands (y=3-x) NR inter-band CA |
ZTE Corporation |
R4-2208713 |
Big CR to reflect the completed ENDC combinations for 3 bands DL with 3 bands UL into TS 38.101-3 |
ZTE Corporation |
R4-2208714 |
TR 37.717-33 v0.8.0 |
ZTE Corporation |
8.16.2 |
UE RF requirements |
|
R4-2208698 |
TP for 37.717-33: DC_8A_n79A-n258A |
ZTE Corporation |
8.17.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2208715 |
Revised WID on Rel-17 Dual Connectivity (DC) of x bands (x=1,2,3) LTE inter-band CA (xDL1UL) and 3 bands NR inter-band CA (3DL1UL) |
ZTE Corporation |
R4-2208716 |
Big CR to reflect the completed DC of x bands (x=1,2,3) LTE inter-band CA (xDL1UL) and 3 bands NR inter-band CA (3DL1UL) into TS 38.101-3 |
ZTE Corporation |
R4-2208717 |
TR 37.717-11-31 v0.8.0 |
ZTE Corporation |
8.17.2 |
UE RF requirements |
|
R4-2207843 |
Draft CR for TS 38.101-3: Addition of missing Tib/Rib values for NR 3 bands EN-DC combinations |
SoftBank Corp. |
R4-2207856 |
TP for TR 37.717-11-31: EN-DC_1-11_n3-n77-n79 |
SoftBank Corp. |
R4-2207857 |
TP for TR 37.717-11-31: EN-DC_8-11_n3-n77-n79 |
SoftBank Corp. |
R4-2208442 |
TP for TR 38.717-11-31 DC_3_n1-n40-n78 |
Samsung, Spark |
R4-2208443 |
TP for TR 38.717-11-31 DC_3_n5-n40-n78 |
Samsung, Spark |
8.18.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2209267 |
Revised WID on Rel-17 Dual Connectivity (DC) of x bands (x=1,2) LTE inter-band CA (xDL1UL) and 4 bands NR inter-band CA (4DL1UL) |
Huawei, HiSilicon |
R4-2209268 |
Big CR on Introduction of completed Dual Connectivity (DC) of x bands (x=1,2) LTE inter-band CA (xDL1UL) and 4 bands NR inter-band CA (4DL1UL) into TS 38.101-3 |
Huawei, HiSilicon |
R4-2209269 |
TR 37.717-11-41 v1.0.0 |
Huawei, HiSilicon |
8.18.2 |
UE RF requirements |
|
R4-2207844 |
Draft CR for TS 38.101-3: Addition of missing Tib values in DC_8_n3-n28-n77-n79 |
SoftBank Corp. |
R4-2207858 |
TP for TR 37.717-11-41: EN-DC_1-8_n3-n28-n77-n79 |
SoftBank Corp. |
8.19.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2209260 |
Revised WID on Band combinations for SA NR Supplementary uplink (SUL), NSA NR SUL, NSA NR SUL with UL sharing from the UE perspective (ULSUP) |
Huawei, HiSilicon |
R4-2209261 |
TR 37.717-00-00 v1.0.0 |
Huawei, HiSilicon |
R4-2209262 |
Big CR on Introduction of completed SUL band combinations into TS 38.101-1 |
Huawei, HiSilicon |
8.19.2 |
UE RF requirements |
|
R4-2208853 |
Draft CR to 38101-1-h50 for SUL general part |
MediaTek Inc. |
R4-2209294 |
Updated TP for 37.717-00-00 to add SUL configuration SUL_n79C-n83A for CA_n28A_SUL_n79C-n83A |
Huawei, HiSilicon, CBN |
R4-2209295 |
Updated TP for 37.717-00-00 to add SUL configuration SUL_n41C-n83A for CA_n28A_SUL_n41C-n83A |
Huawei, HiSilicon, CBN |
R4-2209296 |
Updated TP for 37.717-00-00 to add SUL configuration SUL_n79C-n80A for CA_n3A_SUL_n79C-n80A |
Huawei, HiSilicon |
R4-2209297 |
Updated TP for 37.717-00-00 to add SUL configuration SUL_n78C-n80A for CA_n3A_SUL_n78C-n80A |
Huawei, HiSilicon |
R4-2209298 |
Updated TP for 37.717-00-00 to add SUL configuration SUL_n78C-n84A for CA_n1A_SUL_n78C-n84A |
Huawei, HiSilicon |
R4-2209299 |
Draft CR for 38.101-1 to add SUL configuration SUL_n79C-n95A |
Huawei, HiSilicon |
R4-2209300 |
Draft CR for 38.101-1 to add SUL configuration SUL_n79C-n80A |
Huawei, HiSilicon |
R4-2209301 |
Draft CR for 38.101-1 to add SUL configuration SUL_n41C-n95A |
Huawei, HiSilicon |
R4-2209302 |
TP for 37.717-00-00 CA_n28A-n79A_SUL_n41A-n83A |
Huawei, HiSilicon, CBN |
R4-2209303 |
TP for 37.717-00-00 CA_n28A-n41A_SUL_n79A-n83A |
Huawei, HiSilicon, CBN |
R4-2209304 |
TP for 37.717-00-00 CA_n79A_SUL_n41A-n97A |
Huawei, HiSilicon |
R4-2209305 |
TP for 37.717-00-00 CA_n41A_SUL_n79A-n97A |
Huawei, HiSilicon |
R4-2209306 |
CR for 38.307 to update the release independence for R17 SUL band combinations |
Huawei, HiSilicon |
R4-2209307 |
TP for 37.717-00-00 to update the editorial errors |
Huawei, HiSilicon |
R4-2210746 |
Draft CR to 38101-1-h50 for SUL general part |
MediaTek Inc. |
8.20 |
Band combinations for Uu and V2X con-current operation |
|
R4-2210253 |
Email discussion summary for [103-e][118] NR_LTE_V2X_PC5_combos |
Moderator (CATT) |
R4-2210451 |
Email discussion summary for [103-e][118] NR_LTE_V2X_PC5_combos |
Moderator (CATT) |
8.20.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2208191 |
Draft CR for TS 38.101-1, Introduce new band combination of V2X_n5A-n47A |
CATT |
R4-2208192 |
Draft CR for TS 38.101-3, Introduce new band combinations of V2X_n5A_47A and V2X_5A_n47A |
CATT |
R4-2208193 |
Big CR for TS 38.101-1, Introduce new band combinations of V2X con-current operation |
CATT |
R4-2208194 |
Big CR for TS 38.101-3, Introduce new band combinations of V2X con-current operation |
CATT |
R4-2208660 |
TR37.875 v0.8.0, Band combinations of V2X con-current operation |
CATT |
R4-2210752 |
Draft CR for TS 38.101-1, Introduce new band combination of V2X_n5A-n47A |
CATT |
R4-2210753 |
Draft CR for TS 38.101-3, Introduce new band combinations of V2X_n5A_47A and V2X_5A_n47A |
CATT |
8.20.2 |
UE RF requirements |
|
R4-2207629 |
Calculation of MSD for V2X_n5A-n47A, V2X_5A_n47A and V2X_n5A_47A and accompanying TP |
Qualcomm Incorporated |
R4-2208190 |
TP on coexistence study of V2X_n5A-n47A, V2X_5A_n47A and V2X_n5A_47A |
CATT |
R4-2209355 |
Draft CR for 38.101-1 to update the requirements for V2X con-current band combinations |
Huawei, HiSilicon |
R4-2210754 |
TP on coexistence study of V2X_n5A-n47A, V2X_5A_n47A and V2X_n5A_47A |
CATT |
R4-2210755 |
Draft CR for 38.101-1 to update the requirements for V2X con-current band combinations |
Huawei, HiSilicon |
8.21 |
Adding channel bandwidth support to existing NR bands |
|
R4-2210254 |
Email discussion summary for [103-e][119] NR_bands_R17_BWs |
Moderator (Ericsson) |
R4-2210452 |
Email discussion summary for [103-e][119] NR_bands_R17_BWs |
Moderator (Ericsson) |
R4-2210558 |
WF on adding 100 MHz channel BW in NR-U bands n46 and n96. |
Qualcomm |
R4-2210559 |
Draft CR to TS 38.101-1: adding 100 MHz channel BW for bands n46, n96 and n102 |
Qualcomm, Skyworks |
R4-2210560 |
Draft CR to TS 38.104: adding 100 MHz channel BW for bands n46, n96 and n102 |
Qualcomm |
R4-2210561 |
WF on new channel bandwidths in band n41 and n90 |
T-Mobile USA |
R4-2210562 |
Draft CR to TS 38.101-1: adding 25 and 30 MHz channel BW for band n26 |
Telstra |
R4-2210563 |
Draft CR to TS 38.104: adding 25 and 30 MHz channel BW for band n26 |
Telstra |
R4-2210564 |
Revised Basket WID on adding channel bandwidth support to existing NR bands |
Ericsson |
8.21.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2208903 |
Big CR to TS 38.104: Adding channel BW support in existing NR bands |
Ericsson |
R4-2208904 |
Big CR to TS 38.101-1: Adding channel BW support in existing NR bands |
Ericsson |
8.21.2.1 |
Addition of bandwidth and Tx/Rx requirements |
|
R4-2207708 |
Clarification on UE behavior to new channel bandwidth(s) introduced in later release during initial access |
China Telecom Corporation Ltd. |
R4-2207709 |
Clarification on UE behavior to new channel bandwidth(s) introduced in later release during initial access |
China Telecom Corporation Ltd. |
R4-2208000 |
CR for 38.101-1 Rel17 Minor Correction for n48 NS_27 30MHz inequality |
Qualcomm Incorporated |
R4-2208005 |
n28 25MHz AMPR |
Qualcomm Incorporated |
R4-2208006 |
n28 25MHz REFSENS |
Qualcomm Incorporated |
R4-2208007 |
n26 25/30MHz REFSENS and Coexistence |
Qualcomm Incorporated |
R4-2208402 |
Draft CR for 38.101-1- Addition of 25 MHz for n28 and n83 |
CMCC |
R4-2208852 |
Discussion on n26 supporting 25_30MHz |
MediaTek Inc. |
R4-2209246 |
Discussion on adding 25MHz channel bandwidth in Band n28 |
Huawei, HiSilicon |
R4-2209247 |
Discussion on REFSENS evaluation for band n28 supporting 25MHz |
Huawei, HiSilicon |
R4-2209248 |
Draft CR for 38.101-1 on adding 25MHz channel bandwidth for n28 and n83 |
Huawei, HiSilicon |
R4-2210013 |
Draft CR for 38.101-1: Addition of 5, 25, 35 and 45 MHz for n41 |
T-Mobile USA |
R4-2210234 |
Band n28 25MHz REFSENS |
Skyworks Solutions Inc. |
R4-2210235 |
Adding 25MHz and 30MHz CBW to Band n26 |
Skyworks Solutions Inc. |
R4-2210757 |
Draft CR for 38.101-1: Addition of 5, 25, 35 and 45 MHz for n41 |
T-Mobile USA |
R4-2210758 |
Draft CR for 38.101-1- Addition of 25 MHz for n28 and n83 |
CMCC |
R4-2210759 |
Clarification on UE behavior to new channel bandwidth(s) introduced in later release during initial access |
China Telecom Corporation Ltd. |
8.21.2.2 |
NR-U 100MHz bandwidth |
|
R4-2207714 |
NR-U 100 MHz channel bandwidth for n46 |
Charter Communications, Inc |
R4-2207995 |
Finalizing UE requirement for 100MHz CBW in NRU bands |
Skyworks Solutions Inc. |
R4-2208036 |
NR-U 100 MHz channelization in band n46 |
Qualcomm Incorporated |
R4-2208039 |
Views on NR-U 100MHz in n46 |
Intel Corporation |
R4-2208043 |
Views on NR-U 100MHz in n46 |
Intel Corporation |
R4-2209320 |
NR-U Introduction of 100 MHz CBW |
Apple |
R4-2209644 |
NR-U Triple Punctured Channel SEM for 100 MHz Bandwidth |
CableLabs, Charter Communications |
8.21.3 |
BS RF requirements |
|
R4-2208403 |
Draft CR for 38.104- Addition of 25 MHz for n28 and n83 |
CMCC |
R4-2209249 |
Draft CR for 38.104 on adding 25MHz channel bandwidth for n28 and n83 |
Huawei, HiSilicon |
R4-2210012 |
Draft CR to TS 38.104: Adding new channel BWs in band n41 |
T-Mobile USA |
R4-2210756 |
Draft CR to TS 38.104: Adding new channel BWs in band n41 |
T-Mobile USA |
8.22 |
Introduction of bandwidth combination set 4 (BCS4) for NR |
|
R4-2210255 |
Email discussion summary for [103-e][120] NR_BCS4-Core |
Moderator (Huawei) |
R4-2210453 |
Email discussion summary for [103-e][120] NR_BCS4-Core |
Moderator (Huawei) |
R4-2210565 |
WF on criteria on Rel-17 enhanced MSD table format |
Skyworks Solutions Inc. |
R4-2210566 |
Draft CR for R17 38.101-1 to introduce new table format for MSD due to cross-band isolation |
Skyworks Solutions Inc. |
R4-2210567 |
Draft CR for 38.101-1 to introduce new table format for MSD due to harmonic interference and for SUL |
Huawei, HiSilicon |
R4-2211266 |
Big CR for 38.101-1 on BCS4 |
Huawei, HiSilicon |
8.22.2 |
UE RF requirements for BCS4/BCS5 |
|
R4-2208454 |
Discussion on the reduced MSD configurations for harmonic and cross-band isolation for NR CA |
CHTTL |
R4-2208676 |
Discussion on maximum aggregated channel bandwidth |
Qualcomm Incorporated |
R4-2208681 |
Discussion on improvement on MSD for harmonic and cross-band isolation for NR CA |
ZTE Corporation |
R4-2208858 |
Discussion on the max aggregated CBW of intra-band CA for BCS4/5 |
Xiaomi |
R4-2209358 |
Discussion on simplifying extended MSD table for SUL |
Huawei, HiSilicon |
R4-2209359 |
CR for 38.101-3 to clarify that BCS4 and BCS5 can't be reported together |
Huawei, HiSilicon |
R4-2209360 |
CR for 38.101-1 to introduce the missing requirements for BCS4 |
Huawei, HiSilicon |
R4-2209420 |
CR for 38.101-3 to clarify that BCS4 and BCS5 can't be reported together |
Huawei, HiSilicon |
R4-2209421 |
CR for 38.101-1 to introduce the missing requirements for BCS4 |
Huawei, HiSilicon |
8.23 |
High-power UE operation for fixed-wireless/vehicle-mounted use cases in Band 12, Band 5, Band 13, Band n5, Band n13, and Band n71 |
|
R4-2210256 |
Email discussion summary for [103-e][121] LTE_NR_HPUE_FWVM |
Moderator (Nokia) |
R4-2210454 |
Email discussion summary for [103-e][121] LTE_NR_HPUE_FWVM |
Moderator (Nokia) |
R4-2210568 |
CR for TR 37.828 on release independence |
Nokia |
R4-2210569 |
WF on A-MPR for bands n71 and n85 |
Skyworks |
R4-2211143 |
CR for 38.101-1: Addition of PC1 for NR bands |
T-Mobile USA Inc. |
8.23.1 |
General |
|
R4-2209105 |
Release Independence aspects of high-power UE operation for fixed-wireless/vehicle-mounted use cases |
Nokia |
8.23.3 |
UE RF requirements |
|
R4-2210155 |
Draft CR for 38.101-1: Addition of PC1 for n26, n71 and n85 |
T-Mobile USA Inc. |
R4-2210760 |
Draft CR for 38.101-1: Addition of PC1 for n26, n71 and n85 |
T-Mobile USA Inc. |
8.24 |
High power UE (power class 2) for NR inter-band Carrier Aggregation with 2 bands downlink and 2 bands uplink |
|
R4-2210257 |
Email discussion summary for [103-e][122] NR_PC2_SUL_CA_lowMSD |
Moderator (China Telecom) |
R4-2210455 |
Email discussion summary for [103-e][122] NR_PC2_SUL_CA_lowMSD |
Moderator (China Telecom) |
8.24.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2208335 |
Big CR to 38.101-1 Introduce RF requirements for HPUE CA with 2 bands downlink and x bands uplink (x =1,2) |
China Telecom |
R4-2208643 |
Draft TR 38.841 v1.1.0: High power UE for NR inter-band Carrier Aggregation with 2 bands downlink and x bands uplink (x =1,2) |
Chinatelecom Cloud |
8.24.2 |
UE RF requirements |
|
R4-2207722 |
TP for TR 38.841 Addition of n77 PC1.5 UL for CA_n12-n77 |
AT&T |
R4-2207723 |
TP for TR 38.841 Addition of n77 PC1.5 UL for CA_n14-n77 |
AT&T |
R4-2207724 |
TP for TR 38.841 Addition of n77 PC1.5 UL for CA_n29-n77 |
AT&T |
R4-2207725 |
TP for TR 38.841 Update for n77 PC2 UL and Addition of n77 PC1.5 UL for CA_n30-n77 |
AT&T |
R4-2207935 |
TP for TR 38.841: CA_n13-n77 |
Verizon, Samsung |
R4-2207936 |
TP for TR 38.841: CA_n5-n77 |
Verizon, Samsung |
R4-2207937 |
TP for TR 38.841: CA_n2-n77 |
Verizon, Samsung |
R4-2207939 |
Draft CR for 38.101-1: Addition PC1.5 single uplink for downlink combinations |
Verizon, Samsung |
R4-2209182 |
On Power Class Ambiguity for NR inter-band CA |
Huawei, HiSilicon |
R4-2209183 |
CR to TS38101-1 Resolving power class ambiguity for NR Inter-band CA |
Huawei, HiSilicon |
R4-2210005 |
Draft CR for 38.101-1: Addition of PC2 and PC1.5 for CA_n41-n71 |
T-Mobile USA |
R4-2210006 |
Draft CR for 38.101-1: Addition of n77 PC1.5 for CA_n66-n77 |
T-Mobile USA |
R4-2210007 |
Draft CR for 38.101-1: Addition of PC2 and PC1.5 for CA_n25-n77 |
T-Mobile USA |
R4-2210008 |
Draft CR for 38.101-1: Addition of PC2 and PC1.5 n41 for CA_n41(3A) and CA_n41(A-C) |
T-Mobile USA |
R4-2210009 |
Draft CR for 38.101-1: Addition of n77 UL PC2 and PC1.5 for DL CA_n77(2A) |
T-Mobile USA |
R4-2210010 |
Draft CR for 38.101-1: Addition of PC2 and PC1.5 for CA_n71-n77 |
T-Mobile USA |
R4-2210011 |
Draft CR for 38.101-1: Addition of PC2 and PC1.5 for CA_n41-n77 |
T-Mobile USA |
R4-2210761 |
TP for TR 38.841 Update for n77 PC2 UL and Addition of n77 PC1.5 UL for CA_n30-n77 |
AT&T |
R4-2210762 |
TP for TR 38.841: CA_n13-n77 |
Verizon, Samsung |
R4-2210763 |
Draft CR for 38.101-1: Addition PC1.5 single uplink for downlink combinations |
Verizon, Samsung |
R4-2210764 |
CR to TS38101-1 Resolving power class ambiguity for NR Inter-band CA |
Huawei, HiSilicon |
R4-2210765 |
Draft CR for 38.101-1: Addition of n77 UL PC2 and PC1.5 for DL CA_n77(2A) |
T-Mobile USA |
8.25.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2207698 |
Revised WID on High power UE (power class 2) for EN-DC with 1 LTE band + 1 NR TDD band |
China Unicom |
R4-2207699 |
Big CR on introduction of completed PC2 for EN-DC with 1 LTE band + 1 NR TDD band |
China Unicom |
R4-2207700 |
TR 37.826 v1.2.0 ENDC_UE_PC2_R17_NR_TDD |
China Unicom |
8.25.2 |
UE RF requirements |
|
R4-2208427 |
TP for TR 37.826: update PC2 support for DC_3-3_n78, DC_7-7_n78 |
CHTTL |
8.26.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2209177 |
draft TR 38.842 v0.4.0 |
Huawei, HiSilicon, China Unicom |
R4-2209178 |
Revised WID on NR_UE_PC2_R17_CADC_SUL_xBDL_yBUL |
Huawei, HiSilicon, China Unicom |
R4-2209179 |
Big CR to 38.101-1 Introduce RF requirements for HPUE CA |
Huawei, HiSilicon, China Unicom |
8.26.2 |
UE RF requirements |
|
R4-2207726 |
DraftCR 38.101-1 Addition of PC2 CA Combinations |
AT&T |
R4-2208008 |
CA_n30-n77 MSD NRCA PC2_R17_2BDL_1BUL TR 38.842 |
Qualcomm Incorporated |
8.27.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2209545 |
Revised WID EN-DC PC2 |
Ericsson |
R4-2209550 |
big CR 38.101-3 EN-DC PC2 |
Ericsson |
R4-2209554 |
TR 37.827 v0.5.0 ENDC_PC2_R17_xLTE_yNR |
Ericsson |
R4-2210258 |
Email discussion summary for [103-e][123] NR_PC2_EN-DC |
Moderator (Ericsson) |
R4-2210456 |
Email discussion summary for [103-e][123] NR_PC2_EN-DC |
Moderator (Ericsson) |
8.27.2 |
UE RF requirements |
|
R4-2207938 |
Draft CR for 38.101-1: Addition PC1.5 single uplink for 3DL combinations |
Verizon, Samsung |
R4-2208451 |
TP for TR 37.827: update PC2 support for DC_3-3-7-7_n78 |
CHTTL |
R4-2208452 |
TP for TR 37.827: update PC2 support for DC_3-3-8_n78, DC_7-7-8_n78 |
CHTTL |
R4-2208453 |
TP for TR 37.827: update PC2 support for DC_3-3-7-7-8_n78 |
CHTTL |
R4-2210766 |
Draft CR for 38.101-1: Addition PC1.5 single uplink for 3DL combinations |
Verizon, Samsung |
8.28.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2209755 |
Big CR for TS 38.101-1: Introduce high power UE for NR TDD intra-band CA in FR1 |
Huawei, HiSilicon |
R4-2209756 |
Revised WID for high power UE for NR TDD intra-band CA in FR1 |
Huawei, HiSilicon |
R4-2210725 |
Big CR for TS 38.101-1: Introduce high power UE for NR TDD intra-band CA in FR1 |
Huawei, HiSilicon |
8.28.2 |
UE RF requirements |
|
R4-2209754 |
On requirements for high power UE for NR TDD intra-band CA in FR1 |
Huawei, HiSilicon |
8.29 |
Increasing UE power high limit for CA and DC |
|
R4-2210259 |
Email discussion summary for [103-e][124] NR_Power_Limit_CA_DC |
Moderator (Qualcomm Incorporated) |
R4-2210457 |
Email discussion summary for [103-e][124] NR_Power_Limit_CA_DC |
Moderator (Qualcomm Incorporated) |
R4-2210570 |
LS on testing of increased MOP for CA and DC |
OPPO |
8.29.1 |
General |
|
R4-2209184 |
Views on the solutions for increasing the power limit |
Huawei, HiSilicon |
8.29.2 |
Feasibility and impact study |
|
R4-2208426 |
Scalability and PC per band within a CA for the sum method |
Nokia, Nokia Shanghai Bell |
R4-2208429 |
Consideration on Increasing UE power high limit for CA and DC |
Samsung |
R4-2208605 |
The impact of the increasing UE power high limit for CA and DC |
vivo |
R4-2208748 |
Draft LS to RAN2 on increasing UE power high limit for CA and DC |
Ericsson |
R4-2208851 |
Discussion on increasing UE power high limit for CA and DC |
MediaTek Inc. |
R4-2209377 |
R17 UE power class high limit |
OPPO |
8.29.3 |
UE RF requirements |
|
R4-2207678 |
Further views on increasing UE power high limit for CA and DC |
Apple |
R4-2207906 |
Increased MOP for CA and DC |
InterDigital Communications |
R4-2207990 |
Finalizing increased power for PC2 inter-band CA |
Skyworks Solutions Inc. |
R4-2208336 |
Views on increasing UE output power for CA and DC |
China Telecom |
R4-2208604 |
Further discussion on the RF requirements of the increasing UE power high limit for CA and DC |
vivo |
R4-2208749 |
Amendment of the power class for CA and DC band combinations |
Ericsson |
R4-2209090 |
Discussion on increasing UE maximum power high limit |
Xiaomi |
R4-2209327 |
Draft CR for TS 38.101-1: Enable PC2 inter-band UL CA increasing UE power high limit feature |
Apple |
R4-2210198 |
Increasing the maximum power limit for inter-band UL CA |
Qualcomm Incorporated, Verizon, Vodafone, Deutsche Telekom, US Cellular, T-Mobile USA, AT&T, China Unicom, NTT DOCOMO, INC., China Telecom, Nokia, Nokia Shanghai Bell, CableLabs |
R4-2210199 |
Increasing the maximum power limit for inter-band UL DC |
Qualcomm Incorporated, Verizon, Vodafone, Deutsche Telekom, US Cellular, T-Mobile USA, AT&T, China Unicom, NTT DOCOMO, INC., China Telecom, Nokia, Nokia Shanghai Bell, CableLabs |
R4-2210767 |
Increasing the maximum power limit for inter-band UL CA |
Qualcomm Incorporated, Verizon, Vodafone, Deutsche Telekom, US Cellular, T-Mobile USA, AT&T, China Unicom, NTT DOCOMO, INC., China Telecom, Nokia, Nokia Shanghai Bell, CableLabs |
R4-2210768 |
Increasing the maximum power limit for inter-band UL DC |
Qualcomm Incorporated, Verizon, Vodafone, Deutsche Telekom, US Cellular, T-Mobile USA, AT&T, China Unicom, NTT DOCOMO, INC., China Telecom, Nokia, Nokia Shanghai Bell, CableLabs |
8.30 |
Additional NR bands for UL-MIMO |
|
R4-2210260 |
Email discussion summary for [103-e][125] LTE_NR_Other_WI |
Moderator (Huawei) |
R4-2210458 |
Email discussion summary for [103-e][125] LTE_NR_Other_WI |
Moderator (Huawei) |
R4-2210571 |
LS reply on UE capability for 16QAM for NB-IoT |
Ericsson |
8.30.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2209741 |
Big CR for TS38.101-1: introduction of new UL MIMO bands |
Huawei, HiSilicon |
R4-2209742 |
revised WID Additional NR bands for UL-MIMO in Rel-17 |
Huawei, HiSilicon |
R4-2209743 |
Big CR for TS 38.307: release independent for UL MIMO bands (R17) |
Huawei, HiSilicon |
R4-2210771 |
Big CR for TS 38.307: release independent for UL MIMO bands (R17) |
Huawei, HiSilicon |
8.30.2 |
UE RF requirements |
|
R4-2207992 |
Draft CR to TS 38.101-1 V17.5.0 on introducing missing MPR for NR-U PC5 UL MIMO for n46, n96 and n102 |
Skyworks Solutions Inc. |
R4-2208388 |
Draft CR for n95, n97, n98 and n28 UL MIMO |
CMCC |
R4-2210769 |
Draft CR to TS 38.101-1 V17.5.0 on introducing missing MPR for NR-U PC5 UL MIMO for n46, n96 and n102 |
Skyworks Solutions Inc. |
R4-2210770 |
Draft CR for n95, n97, n98 and n28 UL MIMO |
CMCC |
8.31 |
Simultaneous Rx/Tx band combinations for CA, SUL, MR-DC and NR-DC |
|
R4-2211175 |
CR for TS 38.101-2: update of simultaneous RxTx capability for band combinations |
Huawei, HiSilicon |
8.31.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2209014 |
Big CR to 38.101-1: update of simultaneous RxTx capability for band combinations |
Huawei, HiSilicon |
R4-2209015 |
Big CR to 38.101-2: update of simultaneous RxTx capability for band combinations |
Huawei, HiSilicon |
R4-2209016 |
Big CR to 38.101-3: update of simultaneous RxTx capability for band combinations |
Huawei, HiSilicon |
R4-2209251 |
TR 38.839 v0.3.0 |
Huawei, HiSilicon |
R4-2210775 |
Big CR to 38.101-1: update of simultaneous RxTx capability for band combinations |
Huawei, HiSilicon |
R4-2210776 |
Big CR to 38.101-2: update of simultaneous RxTx capability for band combinations |
Huawei, HiSilicon |
R4-2211229 |
TR 38.839 v0.4.0 |
Huawei, HiSilicon |
R4-2211349 |
Big CR to 38.101-3: update of simultaneous RxTx capability for band combinations |
Huawei, HiSilicon |
8.31.2 |
Identify simultaneous Rx/Tx capabilities for band combinations |
|
R4-2207693 |
draft CR to 38.101-1 on new column for mandatory simultaneous RxTx |
Apple |
R4-2207694 |
draft CR to 38.101-3 on new column for mandatory simultaneous RxTx |
Apple |
R4-2210772 |
draft CR to 38.101-1 on new column for mandatory simultaneous RxTx |
Apple |
R4-2210773 |
draft CR to 38.101-3 on new column for mandatory simultaneous RxTx |
Apple |
R4-2211155 |
CR for updating the note of mandatory simultaneous Rx/Tx capability for FR1 NR-CA combinations (R16) |
KDDI |
R4-2211156 |
CR for updating the note of mandatory simultaneous Rx/Tx capability for FR1 NR-CA combinations (R17) |
KDDI |
8.31.4 |
Define rules for simultaneous Rx/Tx capabilities |
|
R4-2208679 |
Simultaneous Rx/Tx capability for FR1+FR1 FDD-TDD band combination |
ZTE Corporation |
R4-2208850 |
Continue discussion on simultaneous RxTx |
MediaTek Inc. |
R4-2208854 |
Draft CR to 38101-1-h50 for SUL combos supporting simultaneous RxTx correction |
MediaTek Inc. |
R4-2208873 |
Draft CR for clarification on per band pair simultaneous RxTx capability for DC TS 38.101-1 |
NTT DOCOMO, INC |
R4-2209740 |
TP for TR 38.839: update for simultaneous RxTx capability |
Huawei, HiSilicon |
R4-2210774 |
Draft CR to 38101-1-h50 for SUL combos supporting simultaneous RxTx correction |
MediaTek Inc. |
9.1.1 |
General |
|
R4-2207653 |
Our Status (SGS TW) Update for the 3GPP RAN4 5G FR1 SA MIMO OTA Lab Alignment Activity |
SGS Wireless |
R4-2208322 |
3GPP NR FR1 MIMO OTA Performance Test Campaign Template |
CAICT |
R4-2208670 |
Handling of FR2 MIMO OTA |
Qualcomm Incorporated |
R4-2209331 |
Proposal on concluding the Rel-17 NR MIMO OTA WI |
CAICT, OPPO, Huawei, HiSilicon, MediaTek Inc. |
R4-2210338 |
Email discussion summary for [103-e][332] NR_MIMO_OTA |
Moderator (CAICT) |
R4-2210535 |
Email discussion summary for [103-e][332] NR_MIMO_OTA |
Moderator (CAICT) |
R4-2210675 |
WF on NR MIMO OTA |
vivo, CAICT |
R4-2210676 |
Reference curves for FR2 channel model validation |
CMCC, CAICT |
R4-2210933 |
3GPP NR FR1 MIMO OTA Performance Test Campaign Template |
CAICT |
R4-2211132 |
Draft CR to TS38.151 on FR2 channel model validation pass fail limits |
vivo, CAICT |
9.1.2.1 |
Lab alignment for FR1 |
|
R4-2207654 |
MIMO OTA lab alignment results |
Huawei Tech.(UK) Co.. Ltd |
R4-2207690 |
Discussion on FR1 MIMO Lab Alignment Timeline |
Apple |
R4-2208319 |
PAD test results for NR FR1 MIMO OTA lab alignment |
MediaTek Beijing Inc. |
R4-2208320 |
CAICT FR1 MIMO OTA lab alignment results |
CAICT |
R4-2208321 |
Summary of FR1 MIMO OTA lab alignment results |
CAICT |
R4-2208412 |
PAD testing results of CMCC & BUPT joint lab |
CMCC |
R4-2208480 |
Discussion on reference value for FR1 MIMO OTA lab alignment |
Samsung |
R4-2208621 |
Discussion on FR1 MIMO OTA lab alignment activity |
vivo |
R4-2209329 |
Views on FR1 MIMO OTA lab alignment |
CAICT, SAICT |
R4-2209433 |
Reference value for FR1 MIMO OTA Lab alignment |
OPPO |
R4-2209512 |
on remaining issue for FR1 Lab alignment |
Xiaomi |
R4-2209514 |
3GPP NR FR1 MIMO OTA Lab Alignment result from Xiaomi Lab |
Xiaomi |
R4-2210632 |
Way Forward on NTN_Solutions_General |
THALES |
9.1.2.2 |
Performance Requirements for FR1 |
|
R4-2208118 |
on data processing for FR1 MIMO OTA lab alignment |
Huawei Tech.(UK) Co.. Ltd |
R4-2208315 |
Review on FR2 MIMO OTA progress and proposal on simulation formula |
MediaTek Beijing Inc. |
R4-2208413 |
Commercial terminal testing results of CMCC & BUPT joint lab |
CMCC |
R4-2209330 |
TRMS measurement results for bands n41, n78 |
CAICT |
R4-2209513 |
initial test result for FR1 performance requirement |
Xiaomi |
R4-2210934 |
Commercial terminal testing results of CMCC & BUPT joint lab |
CMCC |
9.1.2.3 |
Performance Requirements for FR2 |
|
R4-2208317 |
Review on FR2 MIMO OTA progress and proposal on simulation formula |
MediaTek Beijing Inc. |
R4-2208622 |
Views on FR2 MIMO OTA requirements |
vivo |
R4-2208671 |
FR2 MIMO OTA requirements |
Qualcomm Incorporated |
R4-2208672 |
Summary results for FR2 MIMO OTA |
Qualcomm Incorporated |
R4-2209144 |
Discussion FR2 MIMO OTA performance requirements |
Huawei,HiSilicon |
R4-2209435 |
Views on performance requirement of FR2 MIMO OTA |
OPPO |
R4-2210633 |
WF on remaining issue for SAN RF requirements |
CATT |
9.1.2.4 |
MU assessment for FR1 and FR2 |
|
R4-2208673 |
Draft CR on TS 38.151 for MU of FR2 MIMO OTA |
Qualcomm Incorporated |
R4-2210634 |
WF on NTN Solutions RF conformance |
Ericsson |
R4-2210937 |
Draft CR on TS 38.151 for MU of FR2 MIMO OTA |
Qualcomm Incorporated |
9.1.3.1 |
Testing parameters for Performance |
|
R4-2208624 |
draft CR to TS38.151 on UE mechanical mode |
vivo |
R4-2210935 |
draft CR to TS38.151 on UE mechanical mode |
vivo |
R4-2211338 |
BIG CR to 38.151 |
Vivo, CAICT |
9.1.3.2 |
Optimization of test methodologies |
|
R4-2208623 |
Discussion on UE mechanical mode for foldable smartphones |
vivo |
9.1.3.3 |
Channel model validation |
|
R4-2207689 |
FR1 MIMO Channel Model Validation |
Apple |
R4-2208285 |
FR2 Channel validation targets and pass/fail limits |
Spirent Communications |
R4-2209578 |
FR2 Channel Model Validation Reference and Pass/Fail Limits |
Keysight Technologies UK Ltd |
R4-2210932 |
FR2 Channel validation targets and pass/fail limits |
Spirent Communications |
R4-2210938 |
FR2 Channel Model Validation Reference and Pass/Fail Limits |
Keysight Technologies UK Ltd |
9.2.1 |
General and work plan |
|
R4-2207685 |
TRP-TRS work plan update due to lab alignment delays |
Apple |
R4-2208481 |
TP to TS 38.161 on primary mechanical mode |
Samsung, vivo |
R4-2208626 |
3GPP TS 38.161 v0.3.0 |
vivo |
R4-2208631 |
3GPP TRP/TRS Performance Test Campaign Template |
vivo |
R4-2208639 |
Discussion on OTA Testing for devices with a Time-Averaging Algorithm |
vivo |
R4-2210230 |
NR FR1 TRP TRS updates to test procedure for performance test activity |
Sporton International Inc |
R4-2210339 |
Email discussion summary for [103-e][333] FR1_TRP_TRS_Part1 |
Moderator (vivo) |
R4-2210536 |
Email discussion summary for [103-e][333] FR1_TRP_TRS_Part1 |
Moderator (vivo) |
R4-2210677 |
WF on FR1 TRP TRS |
vivo |
R4-2210678 |
Sporton FR1 TRP/TRS lab alignment measurement results |
Sporton |
R4-2210943 |
3GPP TRP/TRS Performance Test Campaign Template |
vivo |
9.2.2 |
Test methodology maintenance |
|
R4-2207688 |
Discussion on Working scope for Alternative test method |
Apple |
R4-2208659 |
Discussion on the addition of RC in test methodology |
SRTC, Bluetest |
R4-2208661 |
TP to TR 38.834: addition of RC in test methodology |
SRTC, Bluetest |
9.2.2.1 |
SA test methodology |
|
R4-2207683 |
TP to 38.161 on EN-DC and PC2 test case applicability rules |
Apple |
R4-2207684 |
TP to 38.161 on TRP aspects |
Apple |
R4-2208630 |
TP to TS 38.161 on test method |
vivo |
R4-2210939 |
TP to 38.161 on EN-DC and PC2 test case applicability rules |
Apple |
R4-2210940 |
TP to 38.161 on TRP aspects |
Apple |
R4-2210942 |
TP to TS 38.161 on test method |
vivo |
9.2.2.2 |
EN-DC test methodology |
|
R4-2207682 |
Remaining issues with EN-DC configuration for TRP-TRS |
Apple |
R4-2208482 |
Draft CR to TR 38.834 on UE mechanical mode and ENDC example band |
Samsung, OPPO |
R4-2208638 |
CR to TR38.834 on TAS OFF verification procedure |
vivo |
R4-2211142 |
CR to TR38.834 on TAS OFF verification procedure |
vivo, Samsung, R&S, OPPO |
9.2.2.3 |
UE with multiple antennas test methodology |
|
R4-2207686 |
Discussion on Tx Diversity Active Cancellation |
Apple |
R4-2207687 |
draft CR to 38.834 on TRP for TxD UEs |
Apple |
R4-2208282 |
on TRP measurement under TxD |
Huawei Tech.(UK) Co.. Ltd |
R4-2208629 |
Views on test methods for TxD |
vivo |
R4-2208675 |
TRP test method for UEs with Tx diversity |
Qualcomm Incorporated |
R4-2209434 |
The influenced factors for Tx antenna switch ON |
OPPO |
R4-2210340 |
Email discussion summary for [103-e][334] FR1_TRP_TRS_Part2 |
Moderator (OPPO) |
R4-2210537 |
Email discussion summary for [103-e][334] FR1_TRP_TRS_Part2 |
Moderator (OPPO) |
R4-2210679 |
WF on FR1 TRP TRS for UE with multi-antenna |
OPPO |
9.2.3 |
Performance requirements |
|
R4-2208411 |
LADs testing results of CMCC lab |
CMCC |
9.2.3.1 |
Framework for lab alignment and requirements |
|
R4-2207655 |
TRP TRS lab alignment measurement from Huawei |
Huawei Tech.(UK) Co.. Ltd |
R4-2208280 |
on data processing for FR1 TRP and TRS OTA measurement |
Huawei Tech.(UK) Co.. Ltd |
R4-2208323 |
CAICT FR1 TRP/TRS lab alignment measurement results |
CAICT |
R4-2208483 |
On percentile value of FR1 TRP TRS performance campaign |
Samsung |
R4-2208627 |
Further updated Working procedure for TRP TRS requirement development |
vivo |
R4-2208633 |
Analysis of 3GPP TRP TRS lab alignment measurement results |
vivo |
R4-2209382 |
3GPP FR1 TRP/TRS Lab Alignment Measurement Results From SRTC |
SRTC |
R4-2209432 |
Lab alignment criteria for FR1 TRP TRS campaign |
OPPO |
R4-2210145 |
Element FR1 TRP/TRS Lab Alignment Campaign Measurement Results |
Element Materials Technology |
R4-2210352 |
OPPO LAD test results for FR1 TRP/TRS Lab Alignment Campaign |
OPPO |
R4-2210941 |
Further updated Working procedure for TRP TRS requirement development |
vivo |
R4-2210945 |
Analysis of 3GPP TRP TRS lab alignment measurement results |
vivo |
9.2.3.2 |
SA requirements |
|
R4-2208628 |
Measurement results for TRP TRS lab alignment activity |
vivo |
R4-2209431 |
Discussion on deriving performance requirement |
OPPO |
9.2.3.3 |
EN-DC requirements |
|
R4-2208283 |
on FR1 TRP and TRS OTA requirement for ENDC |
Huawei Tech.(UK) Co.. Ltd |
R4-2208632 |
TP to TS 38.161 on Phantoms |
vivo |
R4-2210944 |
TP to TS 38.161 on Phantoms |
vivo |
9.3.1 |
RF core requirement maintenance |
|
R4-2207865 |
CR: Update of UE capability and RRC parameter name for Tx switching |
China Telecom |
R4-2208598 |
Removing square brackets for Intra-band NC UL CA requirments |
vivo |
R4-2209744 |
Big CR to TS 38.307: intra-band CA with MIMO requirements (R17) |
Huawei, HiSilicon |
R4-2209745 |
CR to TS 38.101-1: update of signaling for Tx switching (R17) |
Huawei, HiSilicon |
R4-2210243 |
Email discussion summary for [103-e][107] NR_RF_FR1_enh_maintenance_IntraHPUE |
Moderator (Huawei, HiSilicon) |
R4-2210443 |
Email discussion summary for [103-e][107] NR_RF_FR1_enh_maintenance_IntraHPUE |
Moderator (Huawei, HiSilicon) |
R4-2210547 |
CR for TS 38.101-1: Removing square brackets for Intra-band NC UL CA requirements |
vivo |
R4-2210723 |
CR: Update of UE capability and RRC parameter name for Tx switching |
China Telecom |
R4-2210724 |
Big CR to TS 38.307: intra-band CA with MIMO requirements (R17) |
Huawei, HiSilicon |
R4-2211342 |
CR on Receiver requirements for TX diversity |
Apple |
9.3.3 |
RRM performance requirements |
|
R4-2207867 |
Draft CR: Test case for DL interruptions at 2Tx-2Tx switching between two uplink carriers in FDD+TDD and TDD+TDD inter-band CA |
China Telecom |
R4-2208389 |
Draft CR for introducing test cases for DL Interruptions at UE switching between two uplink bands with two transmit antenna connectors for UL inter-band CA (section A.6.5.7.1C, A.6.5.7.2C) |
CMCC |
R4-2208958 |
Test case for R17 Tx switching enhancement |
Huawei, Hisilicon |
R4-2210277 |
Email discussion summary for [103-e][205] NR_RF_FR1_enh_RRM |
Moderator (Huawei, HiSilicon) |
R4-2210474 |
Email discussion summary for [103-e][205] NR_RF_FR1_enh_RRM |
Moderator (Huawei, HiSilicon) |
R4-2210990 |
Draft CR: Test case for DL interruptions at 2Tx-2Tx switching between two uplink carriers in FDD+TDD and TDD+TDD inter-band CA |
China Telecom |
R4-2210991 |
Test case for R17 Tx switching enhancement |
Huawei, Hisilicon |
R4-2210992 |
Draft CR for introducing test cases for DL Interruptions at UE switching between two uplink bands with two transmit antenna connectors for UL inter-band CA (section A.6.5.7.1C, A.6.5.7.2C) |
CMCC |
9.4.1 |
General |
|
R4-2210263 |
Email discussion summary for [103-e][128] NR_RF_FR2_enh2_Part_1 |
Moderator (Nokia) |
R4-2210460 |
Email discussion summary for [103-e][128] NR_RF_FR2_enh2_Part_1 |
Moderator (Nokia) |
R4-2210573 |
WF on FR2 CA relaxations |
Nokia |
9.4.2 |
UE RF requirements for inter-band CA |
|
R4-2208545 |
PC2 RF requirements for inter-band CA_n257A_n259A based on IBM |
LG Electronics, KT, LG Uplus |
R4-2208546 |
CR on FR2-1 PC2 in n259 for supporting PC2 CA_n257-n259 |
LG Electronics, KT, LG Uplus |
R4-2208644 |
CR on FR2-1 PC2 in n259 for supporting PC2 CA_n257-n259 |
LG Electronics, KT, LG Uplus |
R4-2209107 |
38.101-1: Introduction of 900 MHz to 5G NR for RMR |
Nokia, UIC |
9.4.2.1.1 |
UE relaxation values for DL CA with IBM for CA_n258-n261 |
|
R4-2207637 |
On delta(RIB) for n258+n261 DL inter-CA |
Qualcomm Incorporated |
R4-2207638 |
CR to 38.101-2: FR2+FR2 IBM DLCA for PC1/2/5 |
Qualcomm, Nokia, Verizon, LGE |
R4-2207710 |
UE DL requirements for IBM |
Sony, Ericsson |
R4-2208309 |
Discussion on UE relaxation values for inter-band DL CA for CA_n258-n261 |
MediaTek Beijing Inc. |
R4-2208484 |
EIS requirements for IBM based DL CA_n258-n261 |
Samsung |
R4-2208607 |
Discussion on requirements of n258-n261 |
vivo |
R4-2208682 |
Discussion on relaxation value FR2 inter-band UL CA |
ZTE Corporation |
R4-2208683 |
Discussion on IBM inter-band DL CA_n258-n261 |
ZTE Corporation |
R4-2208750 |
Introduction of requirements for DL inter-band CA for CA_n258-n261 |
Ericsson, Sony |
R4-2208862 |
Discussion on delta RIB for CA_n258-n261 based on IBM |
Xiaomi |
R4-2209106 |
Addition of downlink CA_n258-n261 configuration |
Nokia, Qualcomm Inc |
R4-2209321 |
UE relaxation for CA_n258-n261 with IBM |
Apple |
R4-2209427 |
R17 FR2 Inter-band DL CA requirements for n258+n261 |
OPPO |
R4-2210777 |
CR to 38.101-2: FR2+FR2 IBM DLCA for PC1/2/5 |
Qualcomm, Nokia, Verizon, LGE |
R4-2210778 |
Discussion on delta RIB for CA_n258-n261 based on IBM |
Xiaomi |
R4-2210779 |
Addition of downlink CA_n258-n261 configuration |
Nokia, Qualcomm Inc |
9.4.2.2.1 |
UL CA MPR, relaxation values and Pcmax handling for CA_n257A-n259A and CA_n260-n261 |
|
R4-2207635 |
On MPR and delta(TIB) for FR2+FR2 ULCA |
Qualcomm Incorporated |
R4-2207636 |
CR to 38.101-2 FR2+FR2 ULCA Feature |
Qualcomm, Nokia, Verizon, LGE |
R4-2207711 |
UE UL CA requirements based on IBM |
Sony, Ericsson |
R4-2208311 |
Discussion on inter-band UL CA for PC1 CA_n260-n261 and PC5 CA_n257A-n259A |
MediaTek Beijing Inc. |
R4-2208485 |
EIRP requirements for IBM based UL CA for FWA |
Samsung |
R4-2208606 |
Discussion on FR2 inter-band UL CA |
vivo |
R4-2208863 |
RF requirements for inter-band UL CA_n260-n261 and CA_n257-n259 based on IBM |
Xiaomi |
R4-2209429 |
R17 FR2 Inter-band UL CA requirements |
OPPO |
R4-2210192 |
TIB for inter-band UL CA with IBM |
NTT DOCOMO, INC. |
R4-2210193 |
CR to TS38.101-2 TIB for inter-band UL CA |
NTT DOCOMO, INC. |
R4-2210780 |
CR to 38.101-2 FR2+FR2 ULCA Feature |
Qualcomm, Nokia, Verizon, LGE |
9.4.3 |
UL gaps for self-calibration and monitoring |
|
R4-2210264 |
Email discussion summary for [103-e][129] NR_RF_FR2_enh2_Part_2 |
Moderator (Apple) |
R4-2210461 |
Email discussion summary for [103-e][129] NR_RF_FR2_enh2_Part_2 |
Moderator (Apple) |
R4-2210574 |
WF on UL gap for FR2 |
Apple |
R4-2210575 |
LS on UL gap for FR2 |
Apple |
R4-2210576 |
Draft CR on RF related UL gap for FR2 (38.101-2) |
Apple |
R4-2211221 |
WF on UL gap for FR2 |
Apple |
R4-2211222 |
LS to RAN2 on UL gap in FR2 RF enhancement |
Apple |
9.4.3.1 |
UE Tx power management |
|
R4-2207661 |
On RF requirements for UL Gap |
Qualcomm Incorporated |
R4-2207706 |
draft CR on UL Gap RF requirements |
Qualcomm Incorporated |
R4-2207814 |
UL gaps for Tx power management RF aspect |
Apple |
R4-2208608 |
Discussion on UL gap for Tx power management |
vivo |
R4-2208751 |
UE Tx power management test case for MPE compliance |
Ericsson, Sony |
R4-2208875 |
Draft CR for UL gap for Tx power management RF aspect |
Nokia Denmark |
R4-2208876 |
Requirements and test cases of UE FR2 UL Gap for UE Tx power enhancement |
Nokia Denmark |
R4-2209425 |
R17 FR2 UL gap for power management |
OPPO |
9.4.3.2 |
Coherent UL-MIMO |
|
R4-2207815 |
UL gaps for coherent UL MIMO |
Apple |
R4-2209145 |
Draft CR to 38.101-2 on requirements for coherent UL MIMO |
Huawei,HiSilicon |
R4-2209146 |
Discussion on UL coherent MIMO |
Huawei,HiSilicon |
R4-2209153 |
FR2 UL coherent MIMO |
Anritsu Limited |
R4-2209154 |
Draft CR to add ‘Annex G Difference of relative phase and power errors’ for FR2 UL coherent MIMO |
Anritsu Limited |
R4-2209155 |
Draft CR to add ‘Annex G Difference of relative phase and power errors’ for FR2 UL coherent MIMO |
Anritsu Limited |
R4-2209156 |
Draft CR to add ‘Annex G Difference of relative phase and power errors’ for FR2 UL coherent MIMO |
Anritsu Limited |
R4-2211140 |
Draft CR to add ‘Annex G Difference of relative phase and power errors’ for FR2 UL coherent MIMO |
Anritsu Limited |
9.4.4 |
DC location for intra-band UL CA for both FR2 and FR1 |
|
R4-2207660 |
Offset and DL CA handling for DC location |
Qualcomm Incorporated |
R4-2207679 |
Further views on DC location for intra-band UL CA |
Apple |
R4-2208385 |
Handling of multiple DC locations for intra-band CA |
Nokia, Nokia Shanghai Bell |
R4-2208387 |
[Draft] Reply on LS Reply LS on DC location for >2CC |
Nokia, Nokia Shanghai Bell |
R4-2208609 |
Discussion on remaining issue on DC location |
vivo |
R4-2208610 |
LS on DC location for intra-band CA |
vivo |
R4-2209166 |
Further study on DC location reporting |
Huawei, HiSilicon |
R4-2209424 |
R17 FR2 DC reporting |
OPPO |
R4-2210265 |
Email discussion summary for [103-e][130] NR_RF_FR2_enh2_Part_3 |
Moderator (vivo) |
R4-2210462 |
Email discussion summary for [103-e][130] NR_RF_FR2_enh2_Part_3 |
Moderator (vivo) |
R4-2210782 |
LS on DC location for intra-band CA |
vivo |
9.4.5.1 |
New FR2 CA BW Classes to enable CA operation for mix of 100 and 200 MHz CCs |
|
R4-2207680 |
Further views on new FR2 CA BW classes |
Apple |
R4-2208314 |
Discussion on FR2 mixed-CC CA BW class |
MediaTek Beijing Inc. |
R4-2208486 |
Discussion on CA BW class of mixed 100MHz and 200MHz CCs |
Samsung |
R4-2208752 |
Draft LS to RAN2 on FR2 bandwidth classes covering up to 2400 MHz aggregated bandwidth with mixed carrier bandwidths |
Ericsson, Verizon |
R4-2208753 |
FR2 CA BW classes up to 2400 MHz aggregated BW with mixed channel bandwidths |
Ericsson, Verizon |
R4-2208864 |
Discussion on FR2 new CA BW classes |
Xiaomi |
R4-2208865 |
LS to introduce new FR2 CA BW Classes |
Xiaomi |
R4-2208866 |
Draft CR for TS 38.101-2 to introduction of FR2 new CA BW classes |
Xiaomi |
R4-2209617 |
Discussion on FR2 CA BW class with aggregated BW up to 1600MHz |
ZTE Corporation |
R4-2210783 |
FR2 CA BW classes up to 2400 MHz aggregated BW with mixed channel bandwidths |
Ericsson, Verizon |
R4-2210784 |
LS to introduce new FR2 CA BW Classes |
Xiaomi |
R4-2211267 |
Big CR on NR FR2 enhancement Rel-17 |
Nokia |
9.4.6.1 |
General |
|
R4-2208498 |
Correction for Big CR on RRM requirements for FR2 Inter-band CA |
Nokia, Nokia Shanghai Bell |
R4-2208992 |
DraftCR on correction to interruption requirements for IBM R17 |
Huawei, Hisilicon |
R4-2209788 |
Correction for Big CR on RRM requirements for FR2 Inter-band CA |
Nokia, Nokia Shanghai Bell |
R4-2210124 |
Update of Big CR for RRM requirements of FR2 Inter-band CA |
Ericsson |
R4-2210291 |
Email discussion summary for [103-e][219] NR_RF_FR2_enh2_RRM |
Moderator (Nokia, Nokia Shanghai Bell) |
R4-2210488 |
Email discussion summary for [103-e][219] NR_RF_FR2_enh2_RRM |
Moderator (Nokia, Nokia Shanghai Bell) |
R4-2210606 |
WF on RRM requirements for FR2 Inter-band DL CA and UL CA |
Nokia |
R4-2211078 |
DraftCR on correction to interruption requirements for IBM R17 |
Huawei, Hisilicon |
R4-2211079 |
Correction for Big CR on RRM requirements for FR2 Inter-band CA |
Nokia, Nokia Shanghai Bell |
R4-2211249 |
Big CR on RRM requirements for FR2 RF enhancement |
Nokia |
9.4.6.2 |
Inter-band UL CA for IBM |
|
R4-2208499 |
CR on RRM requirements for IBM inter-band FR2 UL CA |
Nokia, Nokia Shanghai Bell |
R4-2208993 |
Discussion on carrier numbers for FR2 inter-band UL CA |
Huawei, Hisilicon |
R4-2208994 |
DraftCR on number of serving carriers for FR2 inter-band CA R17 |
Huawei, Hisilicon |
R4-2210125 |
Draft CR on RRM requirements for FR2 inter-band UL CA for IBM UE |
Ericsson |
R4-2211080 |
Draft CR on RRM requirements for FR2 inter-band UL CA for IBM UE |
Ericsson |
9.4.6.3 |
UL gaps for self-calibration and monitoring |
|
R4-2207816 |
UL gaps for Tx power management RRM aspect |
Apple |
R4-2207817 |
Draft CR for UL gap for Tx power management RRM aspect |
Apple |
R4-2208590 |
Discussion on remaining aspects for UL Gaps (RRM) |
Nokia, Nokia Shanghai Bell |
R4-2208591 |
CR for UL gaps for Tx power management |
Nokia, Nokia Shanghai Bell |
R4-2208787 |
LS on priority for PHR including MPE indication |
Nokia Corporation |
R4-2210126 |
Discussion on UL gaps prioritization over critical UL signals |
Ericsson |
R4-2210127 |
Draft CR on UL gaps for BPS |
Ericsson |
R4-2210781 |
Draft CR on UL gaps for BPS |
Apple, Ericsson, Nokia |
9.4.7.1 |
Inter-band UL CA for IBM |
|
R4-2209789 |
Discussion on RRM performance requirements for IBM inter-band FR2 UL CA |
Nokia, Nokia Shanghai Bell |
R4-2209790 |
dratCR on UE UL carrier RRC reconfiguration delay for FR2 |
Nokia, Nokia Shanghai Bell |
R4-2210128 |
Scope of RRM tests for UL inter-band CA for IBM |
Ericsson |
R4-2211081 |
dratCR on UE UL carrier RRC reconfiguration delay for FR2 |
Nokia, Nokia Shanghai Bell |
9.4.7.2 |
UL gaps for self-calibration and monitoring |
|
R4-2208595 |
Discussion on test for UL gaps for Tx power management |
Nokia, Nokia Shanghai Bell |
R4-2208778 |
Discussion on performance requirements of UL gap for Tx power management |
ZTE Corporation |
R4-2210129 |
Scope of the RRM test cases for UL gaps for TX power management |
Ericsson |
9.5.1 |
General requirement maintenance |
|
R4-2207983 |
CR to 38.106: Corections to definitons, symbols and abbreviations |
Ericsson |
R4-2208132 |
CR for TS 38.106 R17: clean up of clause 4 |
CATT |
R4-2209600 |
Discussion on the supported bands for NR repeater |
ZTE Corporation |
R4-2209601 |
CR to TS38.106: clarification on the supported operating bands for NR repeater |
ZTE Corporation |
R4-2209805 |
CR to TS 38.106 with corrections to repeater core specification |
Nokia, Nokia Shanghai Bell |
R4-2210016 |
Draft CR Correction to reference point diagram |
Huawei |
R4-2210020 |
Draft CR Terms, symbols and abbreviations |
Huawei |
R4-2210310 |
Email discussion summary for [103-e][304] NR_Repeater_RFMaintenance |
Moderator (CMCC) |
R4-2210507 |
Email discussion summary for [103-e][304] NR_Repeater_RFMaintenance |
Moderator (CMCC) |
R4-2210629 |
WF on remaining issues for RF repeater |
CMCC |
R4-2210829 |
CR to 38.106: Corections to definitons, symbols and abbreviations |
Ericsson |
R4-2210830 |
CR for TS 38.106 R17: clean up of clause 4 |
CATT |
R4-2210836 |
CR to TS38.106: clarification on the supported operating bands for NR repeater |
ZTE Corporation |
R4-2210838 |
CR to TS 38.106 with corrections to repeater core specification |
Nokia, Nokia Shanghai Bell |
R4-2210842 |
Draft CR Terms, symbols and abbreviations |
Huawei |
9.5.2 |
Conductive RF core requirement maintenance |
|
R4-2207979 |
Repeater TX IM power level |
Ericsson |
R4-2207980 |
Draft CR to 38.106: Conducted requirements corrections |
Ericsson |
R4-2208133 |
CR for TS 38.106 R17: clean up of clause 6 |
CATT |
R4-2208406 |
Draft CR for 38.106: add co-existence requirements for input intermodulation |
CMCC |
R4-2208788 |
Discussion on the corrections of unwanted emission for FR1 repeater |
NTT DOCOMO, INC. |
R4-2208789 |
Draft CR for corrections on unwanted emission requirements for FR1 NR repeater |
NTT DOCOMO, INC. |
R4-2208796 |
CR to 38.106: Output power definitions for NR repeaters |
NEC |
R4-2208797 |
CR to 38.106: Regional requirements for NR repeaters |
NEC |
R4-2210017 |
Draft CR OBUE |
Huawei |
R4-2210019 |
Draft CR out of band gain |
Huawei |
R4-2210021 |
Draft CR conducted output power |
Huawei |
R4-2210827 |
Draft CR to 38.106: Conducted requirements corrections |
Ericsson |
R4-2210831 |
CR for TS 38.106 R17: clean up of clause 6 |
CATT |
R4-2210833 |
Draft CR for 38.106: add co-existence requirements for input intermodulation |
CMCC |
R4-2210834 |
Draft CR for corrections on unwanted emission requirements for FR1 NR repeater |
NTT DOCOMO, INC. |
R4-2210835 |
CR to 38.106: Output power definitions for NR repeaters |
NEC |
R4-2210839 |
Draft CR OBUE |
Huawei |
R4-2210841 |
Draft CR out of band gain |
Huawei |
R4-2210843 |
Draft CR conducted output power |
Huawei |
R4-2211339 |
BIG CR to 38.106 maintenance |
CMCC |
9.5.3 |
Radiated RF core requirement maintenance |
|
R4-2207981 |
On uplink power limit for FR2 |
Ericsson |
R4-2207982 |
CR to 38.106: TDD off power radiated requirement correction |
Ericsson |
R4-2208134 |
CR for TS 38.106 R17: clean up of clause 7 |
CATT |
R4-2209804 |
CR to TS 38.106 with OTA intermodulation requirement updates |
Nokia, Nokia Shanghai Bell |
R4-2210018 |
Draft CR Correction to OTA unwanted emissions |
Huawei |
R4-2210022 |
Draft CR radiated output power |
Huawei |
R4-2210828 |
CR to 38.106: TDD off power radiated requirement correction |
Ericsson |
R4-2210832 |
CR for TS 38.106 R17: clean up of clause 7 |
CATT |
R4-2210837 |
CR to TS 38.106 with OTA intermodulation requirement updates |
Nokia, Nokia Shanghai Bell |
R4-2210840 |
Draft CR Correction to OTA unwanted emissions |
Huawei |
R4-2210844 |
Draft CR radiated output power |
Huawei |
9.5.4 |
EMC core requirement maintenance and performance requirement |
|
R4-2208379 |
Discussion on performance assessment and work split of NR Repeater EMC |
ZTE Corporation |
R4-2209140 |
On TDD NR repeater EMC testing |
Nokia, Nokia Shanghai Bell |
9.5.5.1 |
General |
|
R4-2210311 |
Email discussion summary for [103-e][305] NR_Repeater_RFConformance_Part1 |
Moderator (Huawei) |
R4-2210508 |
Email discussion summary for [103-e][305] NR_Repeater_RFConformance_Part1 |
Moderator (Huawei) |
R4-2210630 |
WF on Repeater conformance general issues |
Huawei |
9.5.5.1.1 |
Stimulus signal /Test models |
|
R4-2207971 |
Repeaters test models |
Ericsson |
R4-2208137 |
Discussion of stimulus signals for conducted and radiated |
CATT |
R4-2209602 |
Discussion on NR repeater Stimulus signals |
ZTE Corporation |
R4-2209808 |
Repeater stimulus signals and test models for conformance testing |
Nokia, Nokia Shanghai Bell |
9.5.5.1.2 |
Test configurations |
|
R4-2207970 |
Repeaters test configurations |
Ericsson |
R4-2208136 |
Discussion of test configuration for conducted and radiated |
CATT |
R4-2208410 |
Discussion on conducted test configurations for repeater |
CMCC |
R4-2209603 |
Discussion on NR repeater test configuration |
ZTE Corporation |
R4-2209809 |
Repeaters test configurations |
Nokia, Nokia Shanghai Bell |
9.5.5.1.3 |
Others |
|
R4-2207972 |
Repeaters other aspects of conformance |
Ericsson |
R4-2209604 |
Discussions on NR repeater test cases |
ZTE Corporation |
R4-2209722 |
Repeater TDD switching conformance testing |
Nokia, Nokia Shanghai Bell |
9.5.5.2 |
Conductive conformance Testing |
|
R4-2208135 |
Discussion of drafting specification related issues |
CATT |
R4-2208478 |
Spec skeleton for TS 38.115-1 |
CATT |
R4-2209605 |
Discussion on FR1 NR repeater test conformance testing |
ZTE Corporation |
R4-2210014 |
Repeater conducted testing MU |
Huawei |
R4-2210312 |
Email discussion summary for [103-e][306] NR_Repeater_RFConformance_Part2 |
Moderator (CATT) |
R4-2210509 |
Email discussion summary for [103-e][306] NR_Repeater_RFConformance_Part2 |
Moderator (CATT) |
R4-2210631 |
WF on NR FR1/FR2 repeater measurement system set-up |
ZTE |
R4-2210845 |
Spec skeleton for TS 38.115-1 |
CATT |
R4-2211150 |
WF on NR FR1/FR2 repeater MU and TT |
Huawei |
R4-2211151 |
WF on NR FR1/FR2 repeater declarations |
Nokia |
R4-2211152 |
WF on NR FR1/FR2 repeater test procedures and test issues |
Ericsson |
R4-2211153 |
WF on NR FR1/FR2 repeater test specs draft rules and TP splits |
CATT |
R4-2211223 |
WF on NR FR1/FR2 repeater measurement system set-up |
ZTE |
9.5.5.2.1 |
Transmitted power related requirements |
|
R4-2207973 |
Conformance testing for conducted power |
Ericsson |
R4-2208138 |
Discussion of test setup, MU and TT for FR1 NR repeater |
CATT |
R4-2209723 |
Repeater conducted measurement considerations |
Nokia, Nokia Shanghai Bell |
9.5.5.2.2 |
Emission requirements |
|
R4-2207974 |
Conformance testing for conducted emissions |
Ericsson |
R4-2208139 |
Discussion of FR1 repeater declaration |
CATT |
R4-2209724 |
Applicability of conducted conformance testing |
Nokia, Nokia Shanghai Bell |
9.5.5.2.3 |
Others |
|
R4-2207975 |
Conformance testing for conducted requirements |
Ericsson |
R4-2208140 |
Discussion of other issues for FR1 conformance test |
CATT |
R4-2209725 |
Manufacturer declarations for NR repeater type 1-C |
Nokia, Nokia Shanghai Bell |
9.5.5.3 |
Radiated conformance Testing |
|
R4-2209598 |
Spec skeleton for TS 38.115-2 v.0.0.1 |
ZTE Corporation |
R4-2209599 |
Discussion on the skeleton of FR2 NR repeater spec and work split |
ZTE Corporation |
R4-2209606 |
Discussion on FR2 NR repeater test conformance testing |
ZTE Corporation |
R4-2210015 |
Repeater radiated testing MU |
Huawei |
R4-2210846 |
Spec skeleton for TS 38.115-2 v.0.0.1 |
ZTE Corporation |
9.5.5.3.1 |
Transmitted power related requirements |
|
R4-2207976 |
Conformance testing for radiated power |
Ericsson |
R4-2208141 |
Discussion of radiated test setup, MU and TT for NR repeater |
CATT |
R4-2209726 |
Repeater OTA measurement considerations |
Nokia, Nokia Shanghai Bell |
9.5.5.3.2 |
Emission requirements |
|
R4-2207977 |
Conformance testing for radiated emissions |
Ericsson |
R4-2209727 |
Applicability of radiated conformance testing |
Nokia, Nokia Shanghai Bell |
9.5.5.3.3 |
Others |
|
R4-2207978 |
Conformance testing for radiated requirements |
Ericsson |
R4-2208142 |
Discussion of FR2 repeater declaration |
CATT |
R4-2209257 |
Repeaters OTA Testing |
Qualcomm Incorporated |
R4-2209728 |
Manufacturer declarations for NR repeater type 2-O |
Nokia, Nokia Shanghai Bell |
9.6.1 |
UE RF requirements maintenance |
|
R4-2209063 |
CR: Introduction of RMC for 1024QAM maximum input level |
Ericsson |
9.6.3 |
BS RF conformance testing |
|
R4-2208790 |
Discussion on BS RF conformance requirements for 1024QAM in FR1 |
NEC |
R4-2208791 |
CR to 38.141-1: BS RF conformance requirements for 1024QAM in FR1 |
NEC |
R4-2208792 |
CR to 38.141-2: BS RF conformance requirements for 1024QAM in FR1 |
NEC |
R4-2208793 |
CR to 37.141: BS RF conformance requirements for 1024QAM in FR1 |
NEC |
R4-2208794 |
CR to 37.145-1: BS RF conformance requirements for 1024QAM in FR1 |
NEC |
R4-2208795 |
CR to 37.145-2: BS RF conformance requirements for 1024QAM in FR1 |
NEC |
R4-2209138 |
CR to TS 38.141-2: Introduction of 1024 QAM in FR1 |
Ericsson |
R4-2210700 |
CR to TS 38.141-2: Introduction of 1024 QAM in FR1 |
Ericsson |
9.6.4.1 |
PDSCH requirements |
|
R4-2207794 |
Simulation results for PDSCH demod requirements with 1KQAM |
Apple |
R4-2207795 |
Draft CR for PDSCH demodulation requirements for 1KQAM in TDD |
Apple |
R4-2209064 |
Summary of PDSCH simulation results for DL 1024QAM in FR1 |
Ericsson |
R4-2209065 |
UE demodulation requirements for DL 1024QAM |
Ericsson |
R4-2209175 |
PDSCH Simulation results for 1024QAM FR1 UE Demod Tests |
Qualcomm Incorporated |
R4-2209376 |
Draft CR on Applicability Rules and TDLD30-5 delay profile for FR1 DL 1024QAM PDSCH Requirements |
Qualcomm Incorporated |
R4-2209801 |
Simulation results and discussion on the PDSCH requirements for 1024QAM |
MediaTek inc. |
R4-2209803 |
Draft CR to TS38.101-4, PDSCH requirements for 1024QAM in FR1 FDD |
MediaTek inc. |
R4-2209871 |
Simulation results on 1024QAM PDSCH |
Huawei, HiSilicon |
R4-2210323 |
Email discussion summary for [103-e][317] NR_DL1024QAM_Demod |
Moderator (Ericsson) |
R4-2210520 |
Email discussion summary for [103-e][317] NR_DL1024QAM_Demod |
Moderator (Ericsson) |
R4-2210651 |
WF on DL1024QAM UE demodulation requirement |
Ericsson |
R4-2210652 |
Big CR to 38.101-4: Introduction of FR1 1024QAM UE demodulation and CQI reporting requirements |
Ericsson |
R4-2210897 |
Draft CR for PDSCH demodulation requirements for 1KQAM in TDD |
Apple |
R4-2210898 |
Draft CR on Applicability Rules and TDLD30-5 delay profile for FR1 DL 1024QAM PDSCH Requirements |
Qualcomm Incorporated |
R4-2210899 |
Draft CR to TS38.101-4, PDSCH requirements for 1024QAM in FR1 FDD |
MediaTek inc. |
9.6.4.2 |
SDR requirements |
|
R4-2207796 |
Discussion on SDR requirements with 1KQAM |
Apple |
R4-2209067 |
draft CR: Introduction of SDR requirements for DL 1024QAM |
Ericsson |
R4-2210900 |
draft CR: Introduction of SDR requirements for DL 1024QAM |
Ericsson |
9.6.4.3 |
CQI requirements |
|
R4-2209066 |
CQI reporting requirements for DL 1024QAM |
Ericsson |
R4-2209068 |
draft CR: Introduction of TDD CQI reporting requirements for DL 1024QAM |
Ericsson |
R4-2209176 |
CQI requirements for 1024QAM FR1 UE Demod Tests |
Qualcomm Incorporated |
R4-2209430 |
Draft CR on Applicability Rules for FR1 DL 1024QAM CQI Requirements |
Qualcomm Incorporated |
R4-2209802 |
Simulation results and discussion on the CQI requirements for 1024QAM |
MediaTek inc. |
R4-2209872 |
Discussion and simulation results on 1024QAM CQI |
Huawei, HiSilicon |
R4-2209873 |
Draft CR on FDD CQI reporting cases for 1024QAM and CSI RMC (TS38.101-4, Rel-17) |
Huawei, HiSilicon |
R4-2210901 |
draft CR: Introduction of TDD CQI reporting requirements for DL 1024QAM |
Ericsson |
R4-2210902 |
Draft CR on Applicability Rules for FR1 DL 1024QAM CQI Requirements |
Qualcomm Incorporated |
R4-2210903 |
Draft CR on FDD CQI reporting cases for 1024QAM and CSI RMC (TS38.101-4, Rel-17) |
Huawei, HiSilicon |
9.7.1 |
RRM core requirement maintenance |
|
R4-2207762 |
On FR1 HST remaining issue |
Apple |
R4-2207763 |
CR on L1-SINR measurement in FR1 HST |
Apple |
R4-2208150 |
Discussion on L1-SINR measurements for FR1 HST |
CATT |
R4-2208152 |
CR on FR1 HST core requirements |
CATT |
R4-2208531 |
CR on enhanced requirements for SCell measurement for Rel-17 FR1 HST requirements |
CMCC |
R4-2208959 |
Discussion on L1-SINR in FR1 HST |
Huawei, Hisilicon |
R4-2208960 |
Correction on singaling name for FR1 HST |
Huawei, Hisilicon |
R4-2210292 |
Email discussion summary for [103-e][220] NR_HST_FR1_enh_RRM |
Moderator (CMCC) |
R4-2210489 |
Email discussion summary for [103-e][220] NR_HST_FR1_enh_RRM |
Moderator (CMCC) |
R4-2210607 |
WF on RRM for FR1 HST |
CMCC |
R4-2211083 |
CR on enhanced requirements for SCell measurement for Rel-17 FR1 HST requirements |
CMCC |
9.7.2 |
RRM performance requirements |
|
R4-2207732 |
FR1 HST Performance |
Qualcomm, Inc. |
R4-2207764 |
On FR1 HST test scope |
Apple |
R4-2207871 |
Discussion on Rel-17 HST in FR1 |
MediaTek (Shenzhen) Inc. |
R4-2208151 |
Discussion on RRM test cases for FR1 HST |
CATT |
R4-2208511 |
Initial discussion on performance part for FR1 HST RRM enhancement |
CMCC |
R4-2208512 |
Draft CR on release independent for FR1 HST RRM |
CMCC |
R4-2208513 |
Draft CR on release independent for FR1 HST RRM |
CMCC |
R4-2208516 |
Draft CR on test case for cell reselection to NR inter-frequency for FR1 HST |
CMCC |
R4-2208961 |
Discussion on performance accuracy and test case for FR1 HST |
Huawei, Hisilicon |
R4-2208962 |
Draft CR on measurement accuracy for FR1 HST |
Huawei, Hisilicon |
R4-2209085 |
Further discussion on L1-SINR measurements for Rel-17 FR1 HST CA |
Nokia, Nokia Shanghai Bell |
R4-2209086 |
On RRM Tests for Rel-17 FR1 HST scenarios |
Nokia, Nokia Shanghai Bell |
R4-2209097 |
Testing on CA enhancement RRM requirements for NR HST FR1 |
Ericsson |
R4-2209491 |
Discussion on L1-SINR measurements in R17 FR1 HST |
vivo |
R4-2211082 |
Draft CR on test case for cell reselection to NR inter-frequency for FR1 HST |
CMCC |
9.7.3 |
UE demodulation requirements (38.101-4) |
|
R4-2207797 |
Simulation results for PDSCH CA Requirements in HST |
Apple |
R4-2207798 |
Draft CR on HST DPS CA requirements for 4Rx |
Apple |
R4-2208508 |
CR on PDSCH requirements for HST-SFN CA requirements for 4Rx |
CMCC |
R4-2208514 |
Draft CR on release independent for FR1 HST demodulation |
CMCC |
R4-2208515 |
Draft CR on release independent for FR1 HST demodulation |
CMCC |
R4-2208517 |
Simulation results for FR1 HST CA |
CMCC |
R4-2209069 |
Summary for FR1 HST demodulation results |
Ericsson |
R4-2209070 |
Simulation results of PDSCH demodulation requirements for CA with HST-SFN scenario |
Ericsson |
R4-2209860 |
Simulation results on PDSCH CA scenarios for NR UE HST FR1 performance requirements |
Huawei, HiSilicon |
R4-2209861 |
Draft CR on HST FR1 DPS CA requirements for 2Rx (38.101-4) |
Huawei, HiSilicon |
R4-2209918 |
Draft CR on Applicability Rules for FR1 HST CA Requirements |
Qualcomm Incorporated |
R4-2210160 |
Simulation results for FR1 HST PDSCH CA Tests |
Qualcomm Incorporated |
R4-2210324 |
Email discussion summary for [103-e][318] NR_HST_FR1_Demod |
Moderator (CMCC) |
R4-2210521 |
Email discussion summary for [103-e][318] NR_HST_FR1_Demod |
Moderator (CMCC) |
R4-2210904 |
Draft CR on HST DPS CA requirements for 4Rx |
Apple |
R4-2210905 |
CR on PDSCH requirements for HST-SFN CA requirements for 4Rx |
CMCC |
R4-2210906 |
Draft CR on release independent for FR1 HST demodulation |
CMCC |
R4-2210907 |
Draft CR on release independent for FR1 HST demodulation |
CMCC |
R4-2210908 |
Draft CR on HST FR1 DPS CA requirements for 2Rx (38.101-4) |
Huawei, HiSilicon |
R4-2210909 |
Draft CR on Applicability Rules for FR1 HST CA Requirements |
Qualcomm Incorporated |
R4-2211328 |
Big CR to 38.101-4: Introduction of FR1 HST demodulation requirements |
CMCC |
R4-2211329 |
CR to 38.307: release independent for FR1 HST demodulation (Rel-16) |
CMCC |
R4-2211330 |
CR to 38.307: release independent for FR1 HST demodulation (Rel-17) |
CMCC |
9.8.1 |
UE RF core requirement maintenance |
|
R4-2210244 |
Email discussion summary for [103-e][108] NR_HST_FR2_maintenance |
Moderator (Samsung) |
R4-2210444 |
Email discussion summary for [103-e][108] NR_HST_FR2_maintenance |
Moderator (Samsung) |
9.8.1.2 |
UE Rx requirements |
|
R4-2208504 |
Discussion on Spherical Coverage requirements for FR2 HST |
ZTE Corporation |
9.8.2 |
RRM core requirement maintenance |
|
R4-2207734 |
FR2 HST neighboring cell measurement requirement correction |
Qualcomm, Inc. |
R4-2208156 |
CR on FR2 HST core requirements |
CATT |
R4-2210293 |
Email discussion summary for [103-e][221] NR_HST_FR2_RRM_1 |
Moderator (Nokia, Nokia Shanghai Bell) |
R4-2210490 |
Email discussion summary for [103-e][221] NR_HST_FR2_RRM_1 |
Moderator (Nokia, Nokia Shanghai Bell) |
R4-2210608 |
WF on HST FR2 RRM Core Requirement Maintenance |
Nokia, Nokia Shanghai Bell |
R4-2211085 |
FR2 HST neighboring cell measurement requirement correction |
Qualcomm, Inc. |
R4-2211218 |
FR2 HST neighboring cell measurement requirement correction |
Qualcomm, Inc. |
9.8.2.1 |
General |
|
R4-2207818 |
Discussion on general aspect of FR2 HST |
Apple |
R4-2208153 |
Discussion on remaining issues for FR2 HST |
CATT |
R4-2208843 |
Further Discussion on capability and feature list for FR2 HST UE |
Samsung |
R4-2208844 |
CR to TS38.133 for the applicability of requirement for FR2 HST |
Samsung |
R4-2208963 |
Correction on singaling name for FR2 HST |
Huawei, Hisilicon |
R4-2208964 |
Discussion on capability for HST in FR2 |
Huawei, Hisilicon |
R4-2209332 |
CR for TR 38.854 to remove the squar brackets for identified requirements |
ZTE Corporation |
R4-2209520 |
Discussions on remaining issues in RRM enhancements for FR2 HST |
Nokia, Nokia Shanghai Bell |
R4-2210180 |
Introduction of FR2 HST bands for power class 6 in TS 38.133 |
Ericsson |
R4-2211088 |
CR to TS38.133 for the applicability of requirement for FR2 HST |
Samsung |
9.8.2.2 |
RRC Idle/Inactive and connected state mobility requirements |
|
R4-2207879 |
On Throughput and Bi-directional Scenario-A Mobility Performance |
Nokia, Nokia Shanghai Bell |
R4-2207880 |
CR to TR 38.854 on Bi-directional Scenario-A Mobility Performance |
Nokia, Nokia Shanghai Bell |
R4-2207881 |
CR to TR 38.854 on Throughput Performance in HST FR2 Scenarios |
Nokia, Nokia Shanghai Bell |
R4-2209521 |
CR to TS 38.133: intra-frequency measurements with gaps for for FR2 NR HST |
Nokia, Nokia Shanghai Bell |
9.8.2.3 |
Timing requirements |
|
R4-2207882 |
CR to TR 38.854 on HST FR2 RA-Based Timing Adjustment |
Nokia, Nokia Shanghai Bell |
R4-2207890 |
CR to TS 38.133 on UL Timing Adjustment |
Nokia, Nokia Shanghai Bell |
R4-2207891 |
On HST FR2 UL Timing Adjustment |
Nokia, Nokia Shanghai Bell |
R4-2208346 |
Discussion on timing requirements for HST FR2 |
OPPO |
R4-2208770 |
Discussion on remaining issues of Timing for HST FR2 |
ZTE Corporation |
R4-2208845 |
Discussion on Remaining Issues on Timing Requirements for FR2 HST |
Samsung |
R4-2208846 |
CR to TS38.133 for the corrections on one shot large UL timing adjustment for FR2 Power Class 6 UE |
Samsung |
R4-2211084 |
CR to TS 38.133 on UL Timing Adjustment |
Nokia, Nokia Shanghai Bell |
R4-2211087 |
CR to TR 38.854 on HST FR2 RA-Based Timing Adjustment |
Nokia, Nokia Shanghai Bell |
R4-2211217 |
CR to TS 38.133 on UL Timing Adjustment |
Nokia, Nokia Shanghai Bell |
9.8.2.4 |
Signalling characteristics requirements |
|
R4-2207819 |
Discussion on signalling characteristics requirements |
Apple |
R4-2207821 |
Draft CR for SSB scheduling restriction |
Apple |
R4-2208154 |
Discussion on scheduling restriction on SSB for FR2 HST |
CATT |
R4-2208347 |
Scheduling restriction on SSB |
OPPO |
R4-2208769 |
Discussion on remaining issue of Signaling characteristics for HST FR2 |
ZTE Corporation |
R4-2211086 |
Draft CR for SSB scheduling restriction |
Apple |
9.8.2.5 |
Measurement procedure requirements |
|
R4-2207820 |
Discussion on measurement procedure requirement for FR2 HST |
Apple |
R4-2208771 |
Discussion on Measurement Procedure Requirements for HST FR2 |
ZTE Corporation |
R4-2209524 |
CR to TS 38.133: SSB-based L1-SINR measurements for FR2 NR HST |
Nokia, Nokia Shanghai Bell |
R4-2211089 |
CR to TS 38.133: SSB-based L1-SINR measurements for FR2 NR HST |
Nokia, Nokia Shanghai Bell |
9.8.3 |
RRM performance requirements |
|
R4-2207733 |
FR2 HST RRM |
Qualcomm, Inc. |
R4-2208155 |
Discussion on RRM test cases for FR2 HST |
CATT |
R4-2208348 |
Discussion on performance requirements for FR2 HST |
OPPO |
R4-2208847 |
Discussion on RRM Performance Requirements for FR2 HST |
Samsung |
R4-2208965 |
Discussion on measurement accuracy and test case for FR2 HST |
Huawei, Hisilicon |
R4-2208966 |
Simulation results of measurement accuracy for FR2 HST |
Huawei, Hisilicon |
R4-2209098 |
NR FR2 HST RRM performance requirements |
Ericsson |
R4-2209525 |
Link simulation assumptions for L1 and L3 measurement accuracy for FR2 HST scenarios |
Nokia, Nokia Shanghai Bell |
R4-2209526 |
On RRM Tests for Rel-17 FR2 HST scenarios |
Nokia, Nokia Shanghai Bell |
R4-2210214 |
Simulation results for measurement accuracy for FR2 HST |
Nokia, Nokia Shanghai Bell |
R4-2210294 |
Email discussion summary for [103-e][222] NR_HST_FR2_RRM_2 |
Moderator (Samsung) |
R4-2210491 |
Email discussion summary for [103-e][222] NR_HST_FR2_RRM_2 |
Moderator (Samsung) |
R4-2210609 |
WF on RRM performance requirement for FR2 HST |
Samsung |
R4-2211154 |
Link simulation assumptions for L1 and L3 measurement accuracy for FR2 HST scenarios |
Nokia, Nokia Shanghai Bell |
9.8.4.1 |
UE demodulation requirements |
|
R4-2208074 |
Simulation results summary for Rel-17 FR2 HST UE demod |
Samsung |
R4-2208079 |
Big CR on FR2 HST UE demodulation requirement for TS 38.101-4 |
Samsung |
R4-2209071 |
PDSCH demodulation requirements for HST FR2 |
Ericsson |
R4-2209072 |
draft CR: FRC for PDSCH demodulation requirement for FR2 HST |
Ericsson |
R4-2209862 |
Draft CR on minimum requirements for FR2 PDSCH HST-DPS requirements (38.101-4, Rel-17) |
Huawei, HiSilicon |
R4-2210083 |
CR: FR2 HST channel model |
Qualcomm, Inc. |
R4-2210325 |
Email discussion summary for [103-e][319] NR_HST_FR2_Demod_Part1 |
Moderator (Samsung) |
R4-2210522 |
Email discussion summary for [103-e][319] NR_HST_FR2_Demod_Part1 |
Moderator (Samsung) |
R4-2210653 |
WF on UE demodulation requirement for FR2 HST |
Samsung |
R4-2210654 |
DraftCR to TS 38.101-4: Applicability rules for HST FR2 PDSCH requirements |
Intel |
R4-2210910 |
Draft CR on minimum requirements for FR2 PDSCH HST-DPS requirements (38.101-4, Rel-17) |
Huawei, HiSilicon |
R4-2210911 |
CR: FR2 HST channel model |
Qualcomm, Inc. |
9.8.4.1.1 |
PDSCH requirements under Uni-directional scenario |
|
R4-2208076 |
Simulation results of PDSCH requirement for Rel-17 FR2 HST |
Samsung |
R4-2209863 |
Discussion on UE demodulation requirements for FR2 HST Uni-directional |
Huawei, HiSilicon |
9.8.4.1.2 |
PDSCH requirements under Bi-directional scenario |
|
R4-2209864 |
Discussion on UE demodulation requirements for FR2 HST Bi-directional |
Huawei, HiSilicon |
9.8.4.2 |
BS demodulation requirements |
|
R4-2208075 |
Simulation results summary for Rel-17 FR2 HST BS demod |
Samsung |
R4-2208078 |
Big CR on FR2 HST BS demodulation requirement for TS 38.104 |
Samsung |
R4-2209870 |
Draft CR on HST FR2 BS applicability rule (38.141-2, Rel-17) |
Huawei, HiSilicon |
R4-2210148 |
Big CR to TS 38.141-2 on HST FR2 BS Demodulation Performance Requirements |
Nokia, Nokia Shanghai Bell |
R4-2210326 |
Email discussion summary for [103-e][320] NR_HST_FR2_Demod_Part2 |
Moderator (Nokia, Nokia Shanghai Bell) |
R4-2210523 |
Email discussion summary for [103-e][320] NR_HST_FR2_Demod_Part2 |
Moderator (Nokia, Nokia Shanghai Bell) |
R4-2210655 |
WF on BS demodulation requirement for FR2 HST |
Nokia, Nokia Shanghai Bell |
R4-2210656 |
DraftCR to TS 38.104: HST FR2 PUSCH performance requirements |
Intel Corporation |
R4-2210657 |
DraftCR to TS 38.104: FRC for HST FR2 PUSCH performance requirements |
Intel Corporation |
R4-2210912 |
Draft CR on HST FR2 BS applicability rule (38.141-2, Rel-17) |
Huawei, HiSilicon |
R4-2211127 |
DraftCR to TS 38.141-2: FRC for HST FR2 PUSCH performance requirements |
Intel Corporation |
9.8.4.2.1 |
PUSCH requirements |
|
R4-2207907 |
draftCR to TS 38.104 on HST FR2 Channel Conditions |
Nokia, Nokia Shanghai Bell |
R4-2207908 |
draftCR to TS 38.141-2 on HST FR2 Channel Conditions |
Nokia, Nokia Shanghai Bell |
R4-2207984 |
PUSCH simulation results |
Ericsson |
R4-2207985 |
Draft CR to 38.141-2: Inttroduction of HST PUSCH requirements |
Ericsson, Samsung |
R4-2208077 |
Discussion and simulation results of PUSCH requirement for Rel-17 FR2 HST |
Samsung |
R4-2208080 |
Draft CR on BS Manufacturer declaration for FR2 HST for TS 38.141-2 |
Samsung |
R4-2208223 |
Simulation results for PUSCH demodulation requirements for FR2 HST |
CATT |
R4-2209865 |
Simulation results on PUSCH demodulation requirements for FR2 HST |
Huawei, HiSilicon |
R4-2210120 |
On HST FR2 PUSCH Requirements |
Nokia, Nokia Shanghai Bell |
R4-2210913 |
draftCR to TS 38.104 on HST FR2 Channel Conditions |
Nokia, Nokia Shanghai Bell |
R4-2210914 |
draftCR to TS 38.141-2 on HST FR2 Channel Conditions |
Nokia, Nokia Shanghai Bell |
R4-2210915 |
Draft CR to 38.141-2: Inttroduction of HST PUSCH requirements |
Ericsson, Samsung |
R4-2210916 |
Draft CR on BS Manufacturer declaration for FR2 HST for TS 38.141-2 |
Samsung, Nokia, Nokia Shanghai Bell |
9.8.4.2.2 |
PUSCH with UL timing adjustment requirements |
|
R4-2208195 |
Draft CR for TS 38.104, Introduce performance requirements for UL TA |
CATT |
R4-2208224 |
Discussion on UL TA demodulation requirements for FR2 HST |
CATT |
R4-2208225 |
Draft CR for TS 38.141-2, Introduce performance requirements for UL TA |
CATT |
R4-2209866 |
Simulation results on PUSCH with UL timing adjustment requirements for FR2 HST |
Huawei, HiSilicon |
R4-2210917 |
Draft CR for TS 38.104, Introduce performance requirements for UL TA |
CATT |
R4-2210918 |
Draft CR for TS 38.141-2, Introduce performance requirements for UL TA |
CATT |
9.8.4.2.3 |
PRACH requirements |
|
R4-2209867 |
Simulation results on PRACH demodulation requirements for FR2 HST |
Huawei, HiSilicon |
R4-2209868 |
Draft CR on PRACH minimum requirements for high speed train (38.104, Rel-17) |
Huawei, HiSilicon |
R4-2209869 |
Draft CR on PRACH test requirement for high speed train (38.141-2, Rel-17) |
Huawei, HiSilicon |
9.9 |
Further RRM enhancement for NR and MR-DC |
|
R4-2207766 |
Work plan for R17 FeRRM performance part |
Apple |
R4-2210279 |
Email discussion summary for [103-e][207] NR_RRM_enh2_2 |
Moderator (vivo) |
R4-2210476 |
Email discussion summary for [103-e][207] NR_RRM_enh2_2 |
Moderator (vivo) |
R4-2210583 |
WF on further RRM enhancement for NR and MR-DC – HO with PSCell |
vivo |
R4-2211170 |
LS on clarification of RACH prioritisation rules between LTE and NR-U |
Ericsson |
9.9.1 |
RRM core requirement maintenance |
|
R4-2208092 |
38.133 CR on introduction of SRS antenna port switching (resubmission) |
Nokia, Nokia Shanghai Bell |
R4-2210278 |
Email discussion summary for [103-e][206] NR_RRM_enh2_1 |
Moderator (Apple) |
R4-2210475 |
Email discussion summary for [103-e][206] NR_RRM_enh2_1 |
Moderator (Apple) |
9.9.1.1 |
SRS antenna port switching |
|
R4-2207767 |
CR on SRS antenna port switching in TS38.133 |
Apple |
R4-2208090 |
Interruption requirements at SRS antenna port switching |
Nokia, Nokia Shanghai Bell |
R4-2208093 |
draftCR on interruptions at SRS antenna switching |
Nokia, Nokia Shanghai Bell |
R4-2208313 |
Discussion on interruption due to SRS antenna port switching |
LG Electronics Inc. |
R4-2208316 |
CR on interruption limitation due to SRS antenna switching |
LG Electronics Inc. |
R4-2208935 |
CR on SRS antenna port switching requirements 36.133 |
Huawei, Hisilicon |
R4-2208936 |
Draft CR on SRS antenna port switching requirements 38.133 |
Huawei, Hisilicon |
R4-2209133 |
Draft CR on SRS antenna port switching requirements 38.133 |
Huawei, Hisilicon |
R4-2210130 |
Remaining issue in SRS antenna port switching |
Ericsson |
R4-2210993 |
draftCR on interruptions at SRS antenna switching |
Nokia, Nokia Shanghai Bell |
R4-2210994 |
CR on interruption limitation due to SRS antenna switching |
LG Electronics Inc. |
R4-2210995 |
CR on SRS antenna port switching requirements 36.133 |
Huawei, Hisilicon |
9.9.1.2 |
HO with PSCell |
|
R4-2207769 |
On remaining issues of HO with PScell |
Apple |
R4-2207770 |
CR on HO with PSCell for NE-DC to NE-DC in TS38.133 R17 |
Apple |
R4-2207771 |
CR on HO with PSCell for EN-DC to EN-DC in TS36.133 R17 |
Apple |
R4-2208170 |
Discussion on issues for requirement of HO with PSCell |
CATT |
R4-2208171 |
Completing requirement of HO with PSCell |
CATT |
R4-2208500 |
Correction on HO with PSCell requirements in 38133 |
Nokia, Nokia Shanghai Bell |
R4-2208501 |
Correction on HO with PSCell requirements in 36133 |
Nokia, Nokia Shanghai Bell |
R4-2208530 |
CR on Handover with PSCell |
CMCC |
R4-2208937 |
CR on HO with PSCell requirements |
Huawei, Hisilicon |
R4-2209494 |
CR on R17 core requirements for HO with PSCell |
vivo |
R4-2210131 |
Discussion RRM requirements for handover with PSCell for NR-U |
Ericsson |
R4-2210132 |
CR on requirements for HO with PSCell when PSCell is on CCA in EN-DC to EN-DC scenario |
Ericsson |
R4-2210133 |
CR on requirements for HO with PSCell when PSCell is on CCA in NR SA to EN-DC scenario |
Ericsson |
R4-2210997 |
CR on HO with PSCell for NE-DC to NE-DC in TS38.133 R17 |
Apple |
R4-2210998 |
CR on HO with PSCell for EN-DC to EN-DC in TS36.133 R17 |
Apple |
R4-2210999 |
Completing requirement of HO with PSCell |
CATT |
R4-2211000 |
CR on R17 core requirements for HO with PSCell |
vivo |
R4-2211001 |
CR on requirements for HO with PSCell when PSCell is on CCA in EN-DC to EN-DC scenario |
Ericsson |
R4-2211002 |
CR on requirements for HO with PSCell when PSCell is on CCA in NR SA to EN-DC scenario |
Ericsson |
R4-2211191 |
Correction on HO with PSCell requirements in 36133 |
Nokia, Nokia Shanghai Bell |
9.9.1.3 |
PUCCH SCell activation/deactivation |
|
R4-2207773 |
On remaining issue for PUCCH SCell activation |
Apple |
R4-2207774 |
CR on PUCCH SCell activation in TS38.133 R17 |
Apple |
R4-2207956 |
PUCCH SCell activation and deactivation |
Qualcomm Incorporated |
R4-2208063 |
Discussion on remaining issue about PUCCH SCell activation |
Intel Corporation |
R4-2208087 |
Open issues on PUCCH SCell activation |
Nokia, Nokia Shanghai Bell |
R4-2208088 |
draft CR on PUCCH SCell activation delay |
Nokia, Nokia Shanghai Bell |
R4-2208172 |
Discussion on remaining issues for PUCCH Scell activation |
CATT |
R4-2208173 |
Completing PUCCH SCell activation requirement |
CATT |
R4-2208349 |
Initial discussion on test cases for PUCCH SCell ActivationDeactivation |
OPPO |
R4-2208462 |
Discussion on PUCCH SCell activation and deactivation |
MediaTek Inc. |
R4-2208464 |
CR on PUCCH SCell activation and deactivation delay requirements |
MediaTek Inc. |
R4-2208938 |
Discussion on maintenance for PUCCH SCell activation |
Huawei, Hisilicon |
R4-2208939 |
CR on maintenance for PUCCH SCell activation |
Huawei, Hisilicon |
R4-2210134 |
RRM requirements for SCell activation/deactivation with PUCCH |
Ericsson |
R4-2210135 |
CR on SCell activation/deactivation with PUCCH |
Ericsson |
R4-2210280 |
Email discussion summary for [103-e][208] NR_RRM_enh2_3 |
Moderator (CATT) |
R4-2210477 |
Email discussion summary for [103-e][208] NR_RRM_enh2_3 |
Moderator (CATT) |
R4-2210584 |
WF on further RRM enhancement for NR and MR-DC - PUCCH SCell activation/deactivation requirements |
CATT |
R4-2211013 |
draft CR on PUCCH SCell activation delay |
Nokia, Nokia Shanghai Bell |
R4-2211014 |
CR on PUCCH SCell activation and deactivation delay requirements |
MediaTek Inc. |
R4-2211015 |
CR on maintenance for PUCCH SCell activation |
Huawei, Hisilicon |
R4-2211016 |
CR on SCell activation/deactivation with PUCCH |
Ericsson, Huawei |
R4-2211208 |
WF on further RRM enhancement for NR and MR-DC - PUCCH SCell activation/deactivation requirements |
CATT |
R4-2211209 |
draft CR on PUCCH SCell activation delay |
Nokia, Nokia Shanghai Bell |
9.9.2.1 |
SRS antenna port switching |
|
R4-2207730 |
SRS RRM performance scope |
Qualcomm, Inc. |
R4-2207731 |
SRS configuration correction |
Qualcomm, Inc. |
R4-2207768 |
On test case list for SRS antenna port switching |
Apple |
R4-2208065 |
DraftCR to TS 38.133: NR FR1 interruptions at NR SRS antenna port switching with more than 1 SRS symbol in NR-CA |
Intel Corporation |
R4-2208091 |
Discussion on test cases for SRS antenna port switching |
Nokia, Nokia Shanghai Bell |
R4-2208094 |
draftCR on TC1 SRS antenna switching with 1 SRS symbol in sync EN-DC |
Nokia, Nokia Shanghai Bell |
R4-2208108 |
Draft CR on NR FR1 - E-UTRAN interruptions at NR SRS antenna port switching with 1 SRS symbol in asynchronous NE-DC |
Xiaomi |
R4-2208174 |
Discussion on test for SRS antenna port switching |
CATT |
R4-2208175 |
Test case for Interruptions at NR FR1 one SRS symbol with antenna port switching in asynchronous EN-DC |
CATT |
R4-2208350 |
draft CR on NR FR1-E-UTRAN interruptions at NR SRS antenna port switching with 1 SRS symbol in synchronous NE-DC (TC6) |
OPPO |
R4-2208461 |
Draft CR on TC for interruptions at SRS antenna port switching with more than 1 SRS symbol in async NE-DC |
MediaTek Inc. |
R4-2208520 |
Discussion on test cases for SRS antenna port switching |
CMCC |
R4-2208940 |
Discussion on performance requirements for SRS antenna switching |
Huawei, Hisilicon |
R4-2208941 |
Draft CR on TC for NR SRS antenna port switching with more than 1 SRS symbol in asynchronous EN-DC |
Huawei, Hisilicon |
R4-2209492 |
Discussion on test cases for R17 interruption requirements for SRS antenna switching |
vivo |
R4-2209493 |
draft CR on test cases for NR FR1 interruptions at NR SRS antenna port switching with 1 SRS symbol in NR-CA |
vivo |
R4-2210996 |
On test case list for SRS antenna port switching |
Apple |
9.9.2.2 |
HO with PSCell |
|
R4-2207772 |
Draft CR on TC for HO with PSCell from NR-SA to EN-DC with parallel processing and known FR2 PSCell in TS38.133 R17 |
Apple |
R4-2208064 |
DraftCR to TS 38.133: Handover with PSCell from NR-DC to NR-DC with sequential processing |
Intel Corporation |
R4-2208106 |
CR on test case for Handover with PSCell from NR SA to EN-DC with sequential processing |
Xiaomi |
R4-2208176 |
Discussion on test for HO with PSCell |
CATT |
R4-2208177 |
Test case of handover with PSCell from EN-DC to EN-DC with known target PSCell in FR1 |
CATT |
R4-2208351 |
draft CR on HO with PSCell from NR SA to EN-DC with parallel processing(TC2) |
OPPO |
R4-2208458 |
RRM performance requirements for HO with PSCELL |
Qualcomm Incorporated |
R4-2208502 |
discussion on HO with PSCell performance requirements |
Nokia, Nokia Shanghai Bell |
R4-2208503 |
dratCR on test case for HO with PSCell - TC10 |
Nokia, Nokia Shanghai Bell |
R4-2208518 |
Discussion on test cases for HO with PSCell |
CMCC |
R4-2208942 |
Discussion on performance requirements for HO with PSCell |
Huawei, Hisilicon |
R4-2208943 |
Draft CR on TC for HO with PSCell from NR SA to EN-DC |
Huawei, Hisilicon |
R4-2209495 |
Discussion on test cases for R17 requirements for HO with PSCell |
vivo |
R4-2209496 |
draft CR on test cases for Handover with PSCell from NE-DC to NE-DC with known target PSCell |
vivo |
R4-2209991 |
Draft CR 38.133 on the test case of handover with PSCell from NR-DC to NR-DC with parallel processing |
MediaTek Inc. |
R4-2210114 |
RRM performance requirements for HO with PSCELL |
Qualcomm Incorporated |
R4-2210136 |
TC for HO with PSCell from NE-DC to NE-DC with unknown target PSCell |
Ericsson |
R4-2211003 |
CR on test case for Handover with PSCell from NR SA to EN-DC with sequential processing |
Xiaomi |
R4-2211004 |
Draft CR on TC for HO with PSCell from NR-SA to EN-DC with parallel processing and known FR2 PSCell in TS38.133 R17 |
Apple |
R4-2211005 |
DraftCR to TS 38.133: Handover with PSCell from NR-DC to NR-DC with sequential processing |
Intel Corporation |
R4-2211006 |
Test case of handover with PSCell from EN-DC to EN-DC with known target PSCell in FR1 |
CATT |
R4-2211007 |
draft CR on HO with PSCell from NR SA to EN-DC with parallel processing(TC2) |
OPPO |
R4-2211008 |
dratCR on test case for HO with PSCell - TC10 |
Nokia, Nokia Shanghai Bell |
R4-2211009 |
Draft CR on TC for HO with PSCell from NR SA to EN-DC |
Huawei, Hisilicon |
R4-2211010 |
draft CR on test cases for Handover with PSCell from NE-DC to NE-DC with known target PSCell |
vivo |
R4-2211011 |
Draft CR 38.133 on the test case of handover with PSCell from NR-DC to NR-DC with parallel processing |
MediaTek Inc. |
R4-2211012 |
TC for HO with PSCell from NE-DC to NE-DC with unknown target PSCell |
Ericsson |
9.9.2.3 |
PUCCH SCell activation/deactivation |
|
R4-2207775 |
TC for PUCCH SCell activation and deactivation delay requirements of FR1 unknown PUCCH SCell and one FR1 unknown SCell (All NR cells in FR1) R17 |
Apple |
R4-2207957 |
Performance requirements |
Qualcomm Incorporated |
R4-2208089 |
draftCR on TC3 PUCCH SCell activation of FR2 known cell in SA |
Nokia, Nokia Shanghai Bell |
R4-2208107 |
CR on TC for PUCCH SCell activation and deactivation delay requirements |
Xiaomi |
R4-2208178 |
Discussion on test for PUCCH SCell activation |
CATT |
R4-2208179 |
Test case for PUCCH SCell activation and deactivation delay requirements |
CATT |
R4-2208352 |
Maintenance to requirements for PUCCH SCell activationdeactivation |
OPPO |
R4-2208353 |
draft CR for PUCCH SCell activation and deactivation delay requirements of FR1 known cell for EN-DC (TC10) |
OPPO |
R4-2208463 |
Draft CR on TC for PUCCH SCell activation and deactivation delay requirements of FR1 unknown cell |
MediaTek Inc. |
R4-2208519 |
Discussion on test cases for PUCCH SCell activation/deactivation |
CMCC |
R4-2208944 |
Discussion on performance requirements for PUCCH SCell activation |
Huawei, Hisilicon |
R4-2208945 |
Draft CR on TC for PUCCH SCell activation and deactivation |
Huawei, Hisilicon |
R4-2210137 |
TC for PUCCH SCell activation and deactivation delay requirements of FR2 known cell with FR1 PCell |
Ericsson |
9.10.1 |
RRM core requirement maintenance |
|
R4-2210281 |
Email discussion summary for [103-e][209] NR_MG_enh_1 |
Moderator (MediaTek inc.) |
R4-2210478 |
Email discussion summary for [103-e][209] NR_MG_enh_1 |
Moderator (MediaTek inc.) |
R4-2210585 |
WF on R17 NR MG enhancements – multiple concurrent MGs |
MediaTek inc |
9.10.1.1 |
Pre-configured MG pattern(s) |
|
R4-2208030 |
Open issues in core requirements for pre-configured measurement gaps |
Qualcomm Incorporated |
R4-2208294 |
Discussion on remaining issues of pre-configured gap |
MediaTek inc. |
R4-2208295 |
Maintenance CR on TS38.133 for pre-MG |
MediaTek inc. |
R4-2208354 |
On pre-configured MG |
OPPO |
R4-2208355 |
CR to maintain pre-configured measurement gap in TS 38.133 |
OPPO |
R4-2208459 |
draftCR on Pre-MG core maintenance |
Apple |
R4-2208772 |
Views on pre-configured MG patterns |
ZTE Corporation |
R4-2209203 |
Discussion on remaining issues for pre-configured MG |
Huawei, Hisilicon |
R4-2209204 |
CR on pre-MG related requirements |
Huawei, Hisilicon |
R4-2210167 |
Correction to Pre-MG requirements in TS 38.133 |
Ericsson |
R4-2210231 |
Discussion on requirements for Pre-configured MG patterns |
Nokia, Nokia Shanghai Bell |
R4-2210282 |
Email discussion summary for [103-e][210] NR_MG_Part_2 |
Moderator (Intel Corporation) |
R4-2210479 |
Email discussion summary for [103-e][210] NR_MG_Part_2 |
Moderator (Intel Corporation) |
R4-2210586 |
R17 NR MG enhancements – Pre-configured MG |
Intel |
R4-2210587 |
LS on R17 NR MG enhancements – Pre-configured MG |
OPPO |
R4-2211023 |
draftCR on Pre-MG core maintenance |
Apple |
R4-2211024 |
CR on pre-MG related requirements |
Huawei, Hisilicon |
R4-2211025 |
Correction to Pre-MG requirements in TS 38.133 |
Ericsson |
9.10.1.2 |
Multiple concurrent and independent MG patterns |
|
R4-2207756 |
On multiple concurrent and independent MG patterns |
Apple |
R4-2207757 |
draftCR on concurrent gaps |
Apple |
R4-2208032 |
Open issues in core requirements for multiple concurrent measurement gaps |
Qualcomm Incorporated |
R4-2208066 |
Discussion on concurrent measurement gaps in NR |
Intel Corporation |
R4-2208104 |
Discussion on the remaining issues for concurrent MGs |
Xiaomi |
R4-2208206 |
Discussion on the maintenance for multiple concurrent and independent MG patterns |
CATT |
R4-2208273 |
Issues for multiple concurrent and independent MG pattern maintenance |
vivo |
R4-2208296 |
Discussion on remaining issues of concurrent gaps |
MediaTek inc. |
R4-2208297 |
Maintenance CR on TS38.133 for L1 impact due to concurrent MG |
MediaTek inc. |
R4-2208356 |
On multiple concurrent and independent MG |
OPPO |
R4-2208357 |
CR to maintain concurrent measurement gap in TS 38.133 |
OPPO |
R4-2208522 |
Discussion on multiple concurrent and independent MG patterns |
CMCC |
R4-2208528 |
CR on concurrent measurement gaps |
CMCC |
R4-2208592 |
Discussion on remaining aspects of concurrent measurement gaps |
Nokia, Nokia Shanghai Bell |
R4-2208593 |
CR for remaining aspects of concurrent measurement gaps (section 8) |
Nokia, Nokia Shanghai Bell |
R4-2208594 |
CR for remaining aspects of concurrent measurement gaps (section 9) |
Nokia, Nokia Shanghai Bell |
R4-2208773 |
Views on multiple concurrent and independent MGs |
ZTE Corporation |
R4-2208780 |
Reply LS on coordination of R17 gap features |
ZTE Corporation |
R4-2209205 |
Discussion on remaining issues for multiple concurrent MGs |
Huawei, Hisilicon |
R4-2209206 |
CR on collision handling for concurrent MGs |
Huawei, Hisilicon |
R4-2209449 |
Discussion on Multiple concurrent MG patterns |
Ericsson |
R4-2209450 |
CR on concurrent gaps(9.1.8.2) |
Ericsson |
R4-2211017 |
draftCR on concurrent gaps |
Apple |
R4-2211018 |
CR to maintain concurrent measurement gap in TS 38.133 |
OPPO |
R4-2211019 |
CR on concurrent measurement gaps |
CMCC |
R4-2211020 |
CR for remaining aspects of concurrent measurement gaps (section 8) |
Nokia, Nokia Shanghai Bell |
R4-2211021 |
CR for remaining aspects of concurrent measurement gaps (section 9) |
Nokia, Nokia Shanghai Bell |
R4-2211022 |
CR on collision handling for concurrent MGs |
Huawei, Hisilicon |
9.10.1.3 |
Network Controlled Small Gap |
|
R4-2208298 |
Discussion on remaining issues of NCSG |
MediaTek inc. |
R4-2208299 |
Maintenance CR on TS38.133 for L1 impact due toNCSG |
MediaTek inc. |
R4-2208358 |
CR to maintain measurements with NCSG in TS 38.133 |
OPPO |
R4-2208460 |
draftCR on NCSG core maintenance |
Apple |
R4-2208529 |
CR on inter-frequency measurement with NCSG |
CMCC |
R4-2208774 |
Views on remaining issues of NCSG |
ZTE Corporation |
R4-2209207 |
Discussion on remaining issues for NCSG |
Huawei, Hisilicon |
R4-2209208 |
CR on maintenance of NCSG requirements |
Huawei, Hisilicon |
R4-2210168 |
Correction to NCSG requirements in TS 38.133 |
Ericsson |
R4-2210283 |
Email discussion summary for [103-e][211] NR_MG_enh_3 |
Moderator (Apple) |
R4-2210480 |
Email discussion summary for [103-e][211] NR_MG_enh_3 |
Moderator (Apple) |
R4-2210588 |
WF on NCSG |
Apple |
R4-2210589 |
LS on R17 MG enhancement - NCSG |
Apple |
R4-2211026 |
Maintenance CR on TS38.133 for L1 impact due toNCSG |
MediaTek inc. |
R4-2211027 |
CR to maintain measurements with NCSG in TS 38.133 |
OPPO |
R4-2211028 |
draftCR on NCSG core maintenance |
Apple |
R4-2211029 |
CR on maintenance of NCSG requirements |
Huawei, Hisilicon |
R4-2211030 |
Correction to NCSG requirements in TS 38.133 |
Ericsson |
9.10.2.1 |
Pre-configured MG pattern(s) |
|
R4-2207755 |
On Pre-MG performance |
Apple |
R4-2208031 |
On performance requirements for pre-configured measurement gaps |
Qualcomm Incorporated |
R4-2208067 |
Discussion on NR Pre-configured MG test cases configuration and list |
Intel Corporation |
R4-2208207 |
Test cases for pre-configured MG pattern |
CATT |
R4-2208300 |
Discussion on test case scope for pre-configured gap |
MediaTek inc. |
R4-2208524 |
Discussion on test cases for pre-configured MG pattern(s) |
CMCC |
R4-2208779 |
Discussion on pre-configued MG performance requirements |
ZTE Corporation |
R4-2209209 |
Discussion on test cases for pre-MG |
Huawei, Hisilicon |
R4-2210169 |
RRM test case scenarios for Pre-configured measurement gaps |
Ericsson |
9.10.2.2 |
Multiple concurrent and independent MG patterns |
|
R4-2207758 |
On multiple concurrent and independent MG patterns performance |
Apple |
R4-2208033 |
On performance requirements for multiple concurrent measurement gaps |
Qualcomm Incorporated |
R4-2208068 |
Discussion on NR concurrent MG test cases configuration and list |
Intel Corporation |
R4-2208208 |
Test cases for multiple concurrent and independent MG patterns |
CATT |
R4-2208301 |
Discussion on test case scope for concurrent gaps |
MediaTek inc. |
R4-2208521 |
Discussion on test cases for multiple concurrent and independent MG patterns |
CMCC |
R4-2209210 |
Discussion on test cases for concurrent MGs |
Huawei, Hisilicon |
R4-2209451 |
Test case for multiple concurrent MG patterns |
Ericsson |
9.10.2.3 |
Network Controlled Small Gap |
|
R4-2207759 |
On network controlled small gap performance |
Apple |
R4-2208069 |
Discussion on NCSG test cases configuration and list |
Intel Corporation |
R4-2208209 |
Test cases for NCSG |
CATT |
R4-2208302 |
Discussion on test case scope for NCSG |
MediaTek inc. |
R4-2208457 |
RRM performance requirements for NCSG |
Qualcomm Incorporated |
R4-2208523 |
Discussion on test cases for Network Controlled Small Gap |
CMCC |
R4-2208777 |
Discussion on NCSG performance requirements |
ZTE Corporation |
R4-2209211 |
Discussion on test cases for NCSG |
Huawei, Hisilicon |
R4-2210113 |
RRM performance requirements for NCSG |
Qualcomm Incorporated |
R4-2210170 |
RRM test case scenarios for NCSG |
Ericsson |
9.11.1 |
General |
|
R4-2209417 |
Updated work plan for Further enhancement on NR demodulation performance WI |
China Telecom |
R4-2209738 |
Draft CR to 38_101-4: Abbreviations section |
Nokia, Nokia Shanghai Bell |
R4-2210327 |
Email discussion summary for [103-e][321] NR_perf_enh2_Demod_Part1 |
Moderator (China Telecom) |
R4-2210524 |
Email discussion summary for [103-e][321] NR_perf_enh2_Demod_Part1 |
Moderator (China Telecom) |
R4-2210658 |
Simulation assumptions for CRS-IM (30 kHz SCS TDD) |
CMCC |
R4-2210659 |
WF on the test with only inter-RAT MO configured for scenario 2 |
Huawei, HiSilicon |
R4-2210660 |
Draft Big CR for CRS-IM |
Ericsson |
R4-2210926 |
Updated work plan for Further enhancement on NR demodulation performance WI |
China Telecom |
9.11.2 |
UE demodulation and CSI requirements |
|
R4-2209829 |
Draft CR: Introduction of release independence for MMSE-IRC receiver requirements (TS 38.307 Rel-17) |
Huawei, HiSilicon |
R4-2210951 |
Draft CR: Introduction of release independence for MMSE-IRC receiver requirements (TS 38.307 Rel-17) |
Huawei, HiSilicon |
9.11.2.1 |
MMSE-IRC receiver for inter-cell interference |
|
R4-2209824 |
Draft CR: Introduction of general and applicability section of inter-cell MMSE-IRC receiver (TS 38.101-4 Rel-17) |
Huawei, HiSilicon |
R4-2209831 |
Summary of PDSCH requirements simulation results for inter-cell MMSE-IRC receiver |
Huawei, HiSilicon |
R4-2210342 |
Email discussion summary for [103-e][336] NR_perf_enh2_Demod_Part2 |
Moderator (Ericsson) |
R4-2210539 |
Email discussion summary for [103-e][336] NR_perf_enh2_Demod_Part2 |
Moderator (Ericsson) |
R4-2210681 |
WF on PDSCH demodulation and CSI requirements for inter-cell interference MMSE-IRC |
Ericsson |
R4-2210950 |
Draft CR: Introduction of general and applicability section of inter-cell MMSE-IRC receiver (TS 38.101-4 Rel-17) |
Huawei, HiSilicon |
R4-2211331 |
Big CR for inter-cell MMSE-IRC |
Apple |
9.11.2.1.1 |
PDSCH requirements |
|
R4-2207799 |
Simulation results for PDSCH requirements in intercell interference scenarios |
Apple |
R4-2207800 |
Draft CR on PDSCH demod requirements in ICI-FDD |
Apple |
R4-2208254 |
On general and PDSCH demodulation requirements for inter-cell interference MMSE-IRC |
Nokia, Nokia Shanghai Bell |
R4-2208256 |
Simulation Results on PDSCH demodulation requirements for inter-cell interference MMSE-IRC |
Nokia, Nokia Shanghai Bell |
R4-2208258 |
draftCR to 38_101-4: NR Interference model for enhanced performance requirements |
Nokia, Nokia Shanghai Bell |
R4-2208414 |
Simulation results for inter-cell interference suppressing |
CMCC |
R4-2208415 |
Draft CR for TS38.101-4 PDSCH TDD demodulation requirements for inter-cell interference MMSE-IRC |
CMCC |
R4-2209414 |
On PDSCH requirements for UE MMSE-IRC receiver for inter-cell interference suppression |
China Telecom |
R4-2209415 |
Simulation results on PDSCH demodulation requirements for inter-cell interference MMSE-IRC |
China Telecom |
R4-2209436 |
Remaining issues on PDSCH requirement for inter-cell interference |
Ericsson |
R4-2209437 |
Simulation results on PDSCH performance for inter-cell interference |
Ericsson |
R4-2209791 |
Simulation results and discussion on PDSCH requirements with inter-cell inter-user interference |
MediaTek inc. |
R4-2209820 |
Discussion on PDSCH requirements with IRC receiver for inter-cell interference |
Huawei, HiSilicon |
R4-2209821 |
Simulation results for PDSCH IRC performance requirements for inter-cell interference |
Huawei, HiSilicon |
R4-2210156 |
Views and Simulation Results on Inter-cell Interference PDSCH Tests |
Qualcomm Incorporated |
R4-2210947 |
Draft CR on PDSCH demod requirements in ICI-FDD |
Apple |
R4-2210948 |
draftCR to 38_101-4: NR Interference model for enhanced performance requirements |
Nokia, Nokia Shanghai Bell |
R4-2210949 |
Draft CR for TS38.101-4 PDSCH TDD demodulation requirements for inter-cell interference MMSE-IRC |
CMCC |
9.11.2.1.2 |
CQI requirements |
|
R4-2207801 |
Simulation results for CSI reporting requirements in intercell interference scenarios |
Apple |
R4-2208255 |
On CQI requirements for intercell interference MMSE-IRC |
Nokia, Nokia Shanghai Bell |
R4-2208257 |
Simulation Results on CQI requirements for intercell interference MMSE-IRC |
Nokia, Nokia Shanghai Bell |
R4-2209413 |
On CSI requirements for UE MMSE-IRC receiver for inter-cell interference suppression |
China Telecom |
R4-2209438 |
Remaining issues on CSI reporting requirements for inter-cell interference |
Ericsson |
R4-2209439 |
Simulation results on CSI reporting for inter-cell interference |
Ericsson |
R4-2209441 |
draftCR on CSI reporting test case(TDD) |
Ericsson |
R4-2209443 |
Summary of simulation results for Inter-cell MMSE-IRC CQI reporting |
Ericsson |
R4-2209529 |
Draft CR on Intercell Interfrence FDD CQI Requirements |
Qualcomm Incorporated |
R4-2209792 |
Simulation results and discussion on CQI requirements with inter-cell inter-user interference |
MediaTek inc. |
R4-2209822 |
Discussion on CQI requirements with IRC receiver for inter-cell interference |
Huawei, HiSilicon |
R4-2209823 |
Simulation results for CQI IRC requirements for inter-cell interference |
Huawei, HiSilicon |
R4-2210158 |
Views and Simulation Results for Inter-cell Interference CQI Reporting Tests |
Qualcomm Incorporated |
R4-2210952 |
draftCR on CSI reporting test case(TDD) |
Ericsson |
R4-2210953 |
Draft CR on Intercell Interfrence FDD CQI Requirements |
Qualcomm Incorporated |
9.11.2.2 |
MMSE-IRC receiver for intra-cell inter-user interference |
|
R4-2207802 |
Simulation results for PDSCH requirements in MU-MIMO scenarios |
Apple |
R4-2209412 |
Draft CR on PDSCH 4Rx demod requirements for MU-MIMO IRC |
China Telecom |
R4-2209416 |
Simulation results on UE MMSE-IRC receiver for intra-cell inter-user interference suppression |
China Telecom |
R4-2209440 |
Simulation results on PDSCH performance for intra-cell inter-user interference |
Ericsson |
R4-2209442 |
draftCR on MU-MIMO FRC |
Ericsson |
R4-2209793 |
Simulation results for MMSE-IRC receiver with intra-cell interference |
MediaTek inc. |
R4-2209825 |
Simulation results for IRC receiver for intra-cell inter-user interference |
Huawei, HiSilicon |
R4-2209826 |
Draft CR: Introduction of MU-MIMO Beamforming model (TS 38.101-4 Rel-17) |
Huawei, HiSilicon |
R4-2209827 |
Draft CR: Introduction of 2Rx PDSCH demodulation requirements for MU-MIMO MMSE-IRC (TS 38.104 Rel-17) |
Huawei, HiSilicon |
R4-2209828 |
BigCR for IRC for intra cell inter user MMSE receiver requirements |
Huawei, HiSilicon |
R4-2209830 |
Summary of PDSCH requirements simulation results for MU-MIMO MMSE-IRC receiver |
Huawei, HiSilicon |
R4-2210121 |
Simulation Results for Intra-cell Inter-user Interference Tests |
Qualcomm Incorporated |
R4-2210954 |
Draft CR on PDSCH 4Rx demod requirements for MU-MIMO IRC |
China Telecom |
R4-2210955 |
draftCR on MU-MIMO FRC |
Ericsson |
R4-2210956 |
Draft CR: Introduction of MU-MIMO Beamforming model (TS 38.101-4 Rel-17) |
Huawei, HiSilicon |
R4-2210957 |
Draft CR: Introduction of 2Rx PDSCH demodulation requirements for MU-MIMO MMSE-IRC (TS 38.104 Rel-17) |
Huawei, HiSilicon |
9.11.2.3.1 |
General |
|
R4-2207803 |
Simulation results for CRS-IM requirements |
Apple |
R4-2208050 |
Discussion on CRS-IM requirements for 30 kHz SCS case |
Intel Corporation |
R4-2208259 |
On General for CRS-IM |
Nokia, Nokia Shanghai Bell |
R4-2208261 |
draftCR to 38_101-4: NR CRS-IM 15KHz SCS Scenario - General and applicability sections |
Nokia, Nokia Shanghai Bell |
R4-2208416 |
Discussion on the CRS-IM for NR 30kHz SCS |
CMCC |
R4-2208417 |
Simulation results collection for 30kHz SCS CRS-IM |
CMCC |
R4-2208418 |
LS on UE capability and network assistant signalling for CRS interference mitigation in the scenario with overlapping spectrum for LTE and NR with 30kHz SCS |
CMCC |
R4-2208419 |
Draft CR for introduction of general applicability section of CRS-IM with serving cell 30kHz SCS in TS38.101-4 |
CMCC |
R4-2208420 |
Draft CR on TDD PDSCH CRS-IM demod requirements for Scenario2 with overlapping spectrum for LTE and NR 15kHz SCS |
CMCC |
R4-2209148 |
Draft CR for TS38.101-4 PDSCH Reference Channel for CRS-IM receiver in scenarios with overlapping spectrum for LTE and NR |
ZTE Corporation |
R4-2209405 |
Summary of CRS-IM simulation results (15 kHz SCS FDD and TDD) |
China Telecom |
R4-2209408 |
Simulation results for CRS-IM for 15kHz SCS scenario |
China Telecom |
R4-2209410 |
Draft CR on adding FRC for CRS-IM 15kHz SCS test requirements |
China Telecom |
R4-2209411 |
Draft CR on FDD PDSCH CRS-IM demod requirements for DSS Scenario |
China Telecom |
R4-2209693 |
Discussion on the 30kHz SCS scenario for CRS-IM |
Ericsson |
R4-2209694 |
Simulation results for CRS-IM |
Ericsson |
R4-2209695 |
draft CR to TS 38.101-4: TDD PDSCH CRS-IM demod requirements for DSS Scenario |
Ericsson |
R4-2209794 |
Simulation results and discussion on PDSCH requirements for CRS-IM receiver |
MediaTek inc. |
R4-2209795 |
Draft CR to TS38.101-4, interference model for CRS-IM receiver |
MediaTek inc. |
R4-2209818 |
Discussion on CRS-IM with 30kHz SCS |
Huawei, HiSilicon |
R4-2209819 |
draftCR: Introduction of PDSCH requirements for CRS-IM scenario 2 with 30kHz |
Huawei, HiSilicon |
R4-2210003 |
Simulation results collection for 30kHz SCS CRS-IM |
ZTE Corporation |
R4-2210435 |
LS on UE capability and network assistant signalling for CRS interference mitigation in the scenario with overlapping spectrum for LTE and NR with 30kHz SCS |
CMCC |
R4-2210919 |
draftCR to 38_101-4: NR CRS-IM 15KHz SCS Scenario - General and applicability sections |
Nokia, Nokia Shanghai Bell |
R4-2210920 |
Draft CR for introduction of general applicability section of CRS-IM with serving cell 30kHz SCS in TS38.101-4 |
CMCC |
R4-2210921 |
Draft CR on TDD PDSCH CRS-IM demod requirements for Scenario2 with overlapping spectrum for LTE and NR 15kHz SCS |
CMCC |
R4-2210922 |
Draft CR for TS38.101-4 PDSCH Reference Channel for CRS-IM receiver in scenarios with overlapping spectrum for LTE and NR |
ZTE Corporation |
R4-2210924 |
Draft CR on adding FRC for CRS-IM 15kHz SCS test requirements |
China Telecom |
R4-2210925 |
Draft CR on FDD PDSCH CRS-IM demod requirements for DSS Scenario |
China Telecom |
R4-2210927 |
draft CR to TS 38.101-4: TDD PDSCH CRS-IM demod requirements for DSS Scenario |
Ericsson |
R4-2210928 |
Draft CR to TS38.101-4, interference model for CRS-IM receiver |
MediaTek inc. |
R4-2210930 |
draftCR: Introduction of PDSCH requirements for CRS-IM scenario 2 with 30kHz |
Huawei, HiSilicon |
9.11.2.3.2 |
Test set-up |
|
R4-2208260 |
On Test Setup for CRS-IM |
Nokia, Nokia Shanghai Bell |
R4-2208421 |
Discussion on the test setup for CRS-IM 15kHz |
CMCC |
R4-2209147 |
CRS-IM receiver in scenarios with overlapping spectrum for LTE and NR |
ZTE Corporation |
R4-2209404 |
Simulation assumptions for CRS-IM (for 15kHz FDD and TDD) |
China Telecom |
R4-2209409 |
Discussion on the test setup for CRS-IM requirement definition |
China Telecom |
R4-2209527 |
Summary of CRS-IM simulation results (15 kHz SCS FDD and TDD) |
ZTE Corporation |
R4-2209692 |
Discussion on the test setup for CRS-IM |
Ericsson |
R4-2209815 |
Discussion on test setup for CSI-IM with 15kHz SCS |
Huawei, HiSilicon |
R4-2209816 |
Simulation results for CRS-IM with 15kHz SCS |
Huawei, HiSilicon |
R4-2209817 |
draftCR: Introduction of PDSCH requirements for FDD CRS-IM scenario 2 with 15kHz |
Huawei, HiSilicon |
R4-2210191 |
Views on Test Setup for CRS Interference Mitigation in NR |
Qualcomm Incorporated |
R4-2210923 |
Simulation assumptions for CRS-IM (for 15kHz FDD and TDD) |
China Telecom |
R4-2210929 |
draftCR: Introduction of PDSCH requirements for FDD CRS-IM scenario 2 with 15kHz |
Huawei, HiSilicon |
9.12.1 |
General |
|
R4-2208246 |
Remaining issue for General aspects for SAN |
CATT |
R4-2208333 |
Draft Text Proposal to Update TR 38.863 Chapter 3,6 and 8 |
Samsung |
R4-2208334 |
Draft Text Proposal to Update TR 38.863 structure |
Samsung |
R4-2208640 |
Draft TR 38.863 v0.4.0 |
Samsung |
R4-2208641 |
Draft TS 38.101-5 v0.2.0 |
Samsung |
R4-2208889 |
TP to TR 38.863 - Updates |
Ericsson |
R4-2209676 |
TP to TS 38.108: TS corrections; general parts |
Huawei, HiSilicon |
R4-2209917 |
NR_NTN_solutions work plan |
THALES |
R4-2209990 |
pCR for Annex D - TS 38.108 |
THALES |
R4-2209992 |
Draft text proposal for Clause 3 - TS 38.101-5 |
THALES |
R4-2209994 |
pCR for Clause 3.3 Abbreviations - TS 38.108 |
THALES |
R4-2209995 |
pCR for Clause 4.3 Requirement reference points - TS 38.108 |
THALES |
R4-2210189 |
Draft TS 38.108 v0.2.0 |
THALES |
R4-2210313 |
Email discussion summary for [103-e][307] NTN_Solutions_General |
Moderator (THALES) |
R4-2210510 |
Email discussion summary for [103-e][307] NTN_Solutions_General |
Moderator (THALES) |
R4-2210847 |
TP to TR 38.863 - Updates |
Ericsson |
R4-2210849 |
pCR for Clause 4.3 Requirement reference points - TS 38.108 |
THALES |
R4-2210850 |
pCR for Annex D - TS 38.108 |
THALES |
R4-2210851 |
Draft text proposal for Clause 3 - TS 38.101-5 |
THALES |
R4-2210852 |
NR_NTN_solutions work plan |
THALES |
R4-2211133 |
Draft Text Proposal to Update TR 38.863 Chapter 3,6 and 8 |
Samsung |
R4-2211134 |
Draft Text Proposal to Update TR 38.863 structure |
Samsung |
R4-2211343 |
Draft TS 38.108 v0.2.0 |
THALES |
9.12.2 |
Coexistence aspects |
|
R4-2209997 |
Draft text proposal for Clause 6.1 Coexistence Figures - TR 38.863 |
THALES |
R4-2210228 |
Draft text proposal for Clauses 6.4 and 6.5 Corrections Typos - TR 38.863 |
THALES |
R4-2210848 |
Draft text proposal for Clause 6.1 Coexistence Figures - TR 38.863 |
THALES |
9.12.3 |
Satellite Access Node RF requirements |
|
R4-2208888 |
pCR to TS 38.108 - Alignement |
Ericsson |
R4-2210314 |
Email discussion summary for [103-e][308] NTN_Solutions_SANRF |
Moderator (CATT) |
R4-2210511 |
Email discussion summary for [103-e][308] NTN_Solutions_SANRF |
Moderator (CATT) |
R4-2210856 |
pCR to TS 38.108 - Alignement |
Ericsson |
9.12.3.1 |
TX requirements for radiated characteristics |
|
R4-2208883 |
NTN - SAN TX radiated requirements: remaining issues |
Ericsson |
R4-2208887 |
pCR to TS 38.108 - Transmitter spurious requirement |
Ericsson |
R4-2209923 |
On SAN Spurious Emission requirements for Radiated Characteristics |
Nokia, Nokia Shanghai Bell |
R4-2210855 |
pCR to TS 38.108 - Transmitter spurious requirement |
Ericsson |
9.12.3.2 |
RX requirements for radiated characteristics |
|
R4-2210059 |
pCR for Clause 10.6.2 Minimum requirement for SAN type 1-O - TS 38.108 |
THALES |
R4-2210159 |
Draft text proposal for Clause 7.3.3.3.1 OTA sensitivity - TR 38.863 |
THALES |
R4-2210161 |
Draft text proposal for Clause 7.3.3.3.2 OTA reference sensitivity - TR 38.863 |
THALES |
R4-2210162 |
Draft text proposal for Clause 7.3.3.3.3 OTA dynamic range - TR 38.863 |
THALES |
R4-2210163 |
Draft text proposal for Clause 7.3.3.3.2 OTA reference sensitivity - TR 38.863 |
THALES |
R4-2210164 |
Draft text proposal for Clause 7.3.3.3.7 OTA receiver intermodulation - TR 38.863 |
THALES |
R4-2210165 |
Draft text proposal for Clause 7.3.3.3.8 OTA in-channel selectivity - TR 38.863 |
THALES |
R4-2210213 |
Draft text proposal for Clause 7.3.3.3.4 OTA in-band selectivity and blocking - TR 38.863 |
THALES |
R4-2210864 |
pCR for Clause 10.6.2 Minimum requirement for SAN type 1-O - TS 38.108 |
THALES |
R4-2210867 |
Draft text proposal for Clause 7.3.3.3.1 OTA sensitivity - TR 38.863 |
THALES |
R4-2210868 |
Draft text proposal for Clause 7.3.3.3.2 OTA reference sensitivity - TR 38.863 |
THALES |
R4-2210869 |
Draft text proposal for Clause 7.3.3.3.3 OTA dynamic range - TR 38.863 |
THALES |
R4-2210870 |
Draft text proposal for Clause 7.3.3.3.7 OTA receiver intermodulation - TR 38.863 |
THALES |
R4-2210871 |
Draft text proposal for Clause 7.3.3.3.8 OTA in-channel selectivity - TR 38.863 |
THALES |
R4-2210872 |
Draft text proposal for Clause 7.3.3.3.4 OTA in-band selectivity and blocking - TR 38.863 |
THALES |
R4-2211145 |
Draft text proposal for Clause 7.3.3.3.2 OTA reference sensitivity - TR 38.863 |
THALES |
R4-2211146 |
Draft text proposal for Clause 7.3.3.3.2 OTA reference sensitivity - TR 38.863 |
THALES |
9.12.3.3 |
Tx requirements for conducted characteristics |
|
R4-2208247 |
Open issue on conducted requirement for SAN |
CATT |
R4-2208248 |
Open issue on radiated requirement for SAN |
CATT |
R4-2208249 |
TP for 38.863: clause 7.3.2 Conducted transmission characteristics |
CATT |
R4-2208250 |
TP for 38.108: clause 6 on unwanted emissions |
CATT |
R4-2208882 |
NTN - SAN TX conducted requirements: remaining issues |
Ericsson |
R4-2209361 |
Discussion on SAN OoB mask and spurious emission requirements |
Huawei, HiSilicon, Thales |
R4-2209528 |
TP to TS 38.108 on 6.0 Conducted transmitter characteristics |
HUGHES Network Systems Ltd; Hughes/EchoStar |
R4-2209592 |
Further discussion on conducted Tx requirements of satellite access node |
ZTE Corporation |
R4-2209677 |
TP to TS 38.108: TS corrections; RF requirements |
Huawei, HiSilicon |
R4-2209924 |
On SAN Spurious Emission requirements for Conducted Characteristics |
Nokia, Nokia Shanghai Bell |
R4-2209999 |
pCR for Clause 6.6.3 Adjacent Channel Leakage Power Ratio - TS 38.108 |
THALES |
R4-2210000 |
Tentative pCR for Clause 6.6 Unwanted emissions and Clause 6.6.4 OBUE - TS 38.108 |
THALES |
R4-2210001 |
pCR for Clause 6.6.5 Transmitter spurious emissions - TS 38.108 |
THALES |
R4-2210004 |
Draft text proposal for Clause 7.3.2.2.5 Transmitter spurious emissions - TR38.863 |
THALES |
R4-2210082 |
Discussion on SAN OBUE |
THALES |
R4-2210090 |
Discussion on SAN Spurious Emissions |
THALES |
R4-2210110 |
On SAN OBUE definition using ITU-R recommendation |
THALES |
R4-2210116 |
Tentative draft pCR for Clause 7.3.2.2.4.2 Operating band unwanted emissions - TR 38.863 |
THALES |
R4-2210154 |
Draft text proposal for Clause 7.3.2.2.1 SAN output power - TR 38.863 |
THALES |
R4-2210216 |
Draft TP for TS 38.108 Section 6.6.4 Operating band unwanted emissions |
Inmarsat |
R4-2210853 |
TP for 38.863: clause 7.3.2 Conducted transmission characteristics |
CATT |
R4-2210854 |
TP for 38.108: clause 6 on unwanted emissions |
CATT |
R4-2210857 |
TP to TS 38.108 on 6.0 Conducted transmitter characteristics |
HUGHES Network Systems Ltd; Hughes/EchoStar |
R4-2210860 |
Draft text proposal for Clause 7.3.2.2.5 Transmitter spurious emissions - TR38.863 |
THALES |
R4-2210865 |
Tentative draft pCR for Clause 7.3.2.2.4.2 Operating band unwanted emissions - TR 38.863 |
THALES |
R4-2210866 |
Draft text proposal for Clause 7.3.2.2.1 SAN output power - TR 38.863 |
THALES |
R4-2210873 |
Draft TP for TS 38.108 Section 6.6.4 Operating band unwanted emissions |
Inmarsat |
R4-2211135 |
TP to TS 38.108: TS corrections; RF requirements |
Huawei, HiSilicon |
9.12.3.4 |
Rx requirements for conducted characteristics |
|
R4-2208663 |
TP to TS 38.108 on Conducted receiver characteristics |
ZTE Corporation |
R4-2209678 |
TP to TR 38.863: Conducted reference sensitivity |
Huawei, HiSilicon |
R4-2209679 |
TP to TR 38.863: Conducted Rx dynamic range |
Huawei, HiSilicon |
R4-2210030 |
pCR for Clause 7.4 In-band selectivity and blocking - TS 38.108 |
THALES |
R4-2210042 |
pCR for Clause 7.5 Out-of-band blocking - TS 38.108 |
THALES |
R4-2210049 |
pCR for Clause 7.6 Receiver spurious emissions - TS 38.108 |
THALES |
R4-2210858 |
TP to TR 38.863: Conducted reference sensitivity |
Huawei, HiSilicon |
R4-2210859 |
TP to TR 38.863: Conducted Rx dynamic range |
Huawei, HiSilicon |
R4-2210861 |
pCR for Clause 7.4 In-band selectivity and blocking - TS 38.108 |
THALES |
R4-2210862 |
pCR for Clause 7.5 Out-of-band blocking - TS 38.108 |
THALES |
R4-2210863 |
pCR for Clause 7.6 Receiver spurious emissions - TS 38.108 |
THALES |
9.12.4 |
Satellite Access Node RF conformance testing |
|
R4-2210315 |
Email discussion summary for [103-e][309] NTN_Solutions_RFConformance |
Moderator (Ericsson) |
R4-2210512 |
Email discussion summary for [103-e][309] NTN_Solutions_RFConformance |
Moderator (Ericsson) |
9.12.4.1 |
General and work plan |
|
R4-2208251 |
Skeleton for TS 38.181 |
CATT |
R4-2209593 |
Initial discussion on SAN conformance testing: general part |
ZTE Corporation |
R4-2209680 |
Structure of the NTN SAN conformance testing specification |
Huawei, HiSilicon |
R4-2210034 |
Initial considerations on SAN conformance testing - general requirements |
Ericsson |
R4-2210039 |
Further discussion on the Normal and Extreme conditions testing |
Huawei, HiSilicon |
R4-2210040 |
TP to TS 38.108: removal of extreme conditions requirements |
Huawei, HiSilicon |
R4-2211202 |
TP to TS 38.108: removal of extreme conditions requirements |
Huawei, HiSilicon |
9.12.4.2 |
Conductive conformance Testing |
|
R4-2208252 |
General consideration on conductive conformance testing for SAN |
CATT |
R4-2209594 |
Initial discussion on SAN conformance testing: conducted part |
ZTE Corporation |
R4-2210035 |
Initial considerations on SAN conformance testing - conducted requirements |
Ericsson |
9.12.4.3 |
Radiated conformance Testing |
|
R4-2208253 |
General consideration on radiated conformance testing for SAN |
CATT |
R4-2209595 |
Initial discussion on SAN conformance testing: radiated part |
ZTE Corporation |
R4-2210036 |
Initial considerations on SAN conformance testing - OTA requirements |
Ericsson |
9.12.5 |
UE RF requirements |
|
R4-2208886 |
pCR to TS 38.101-5 - Alignement |
Ericsson |
R4-2210316 |
Email discussion summary for [103-e][310] NTN_Solutions_UERF |
Moderator (ZTE) |
R4-2210513 |
Email discussion summary for [103-e][310] NTN_Solutions_UERF |
Moderator (ZTE) |
R4-2210635 |
WF on remaining issue of NTN UE RF |
ZTE |
R4-2210636 |
TP to TR 38.863: coexistence issues between NTN and TN from Rel-17 RAN4 study. |
Huawei |
R4-2211176 |
TP for 38.101-5 on frequency error |
Qualcomm |
R4-2211220 |
TP for 38.101-5 on frequency error |
Qualcomm |
9.12.5.1 |
TX requirements |
|
R4-2207967 |
Measurements for n255 A-MPR evaluation |
Ligado Networks |
R4-2207968 |
Updates to TS 38.101-5 related to n255 A-MPR clause |
Ligado Networks |
R4-2207969 |
TP for TR 38.863: Updates to n255 A-MPR Clause |
Ligado Networks |
R4-2208400 |
Discussion on NS signaling for n256 NTN UE |
CMCC |
R4-2208662 |
TP to TS 38.101-5 on Conducted transmitter characteristics |
ZTE Corporation |
R4-2208674 |
Discussion on NTN UE Tx RF requirements |
Qualcomm Incorporated |
R4-2208884 |
NTN - UE RF TX: remaining issues |
Ericsson |
R4-2209143 |
n256 co-existence and filter implementation aspects |
Skyworks Solutions Inc. |
R4-2209362 |
Discussion on Spurious emissions for protected bands UE co-existence with draft LS |
Huawei, HiSilicon |
R4-2209365 |
TP for 38.863 on UE antenna characteristics for satellite access |
Huawei, HiSilicon |
R4-2209366 |
TP for 38.101-5 on Output RF spectrum emissions for satellite UE except for UE coexistence |
Huawei, HiSilicon |
R4-2209367 |
TP for 38.101-5 on Spurious emissions for UE coexistence |
Huawei, HiSilicon |
R4-2209596 |
Further discussion on NTN UE Tx RF requirements |
ZTE Corporation |
R4-2209715 |
Requirements for spurious emissions for UE co-existence n256 |
HUGHES Network Systems Ltd; Hughes/EchoStar |
R4-2209922 |
On NTN UE frequency error reference point |
Nokia, Nokia Shanghai Bell |
R4-2210875 |
TP for TR 38.863: Updates to n255 A-MPR Clause |
Ligado Networks |
R4-2210876 |
Updates to TS 38.101-5 related to n255 A-MPR clause |
Ligado Networks |
R4-2210877 |
TP for 38.101-5 on Spurious emissions for UE coexistence |
Huawei, HiSilicon |
9.12.5.2 |
RX requirements |
|
R4-2208378 |
Discussion on UE RX REFSENS and OOBB for band n256 |
Mediatek India Technology Pvt. |
R4-2208476 |
TP to update TS 38.101-5 clause 7.6.3 on OOBB |
Mediatek India Technology Pvt. |
R4-2208885 |
NTN - UE RF RX: remaining issues |
Ericsson |
R4-2209087 |
Updates for TS38.101-5 on out of band blocking requirement for NTN UE |
Xiaomi |
R4-2209088 |
Discussion on out of band blocking requirements for NTN UE |
Xiaomi |
R4-2209089 |
TP for 38.863 on general part for NTN UE conducted receiver characteristics |
Xiaomi |
R4-2209363 |
Discussion on UE requirements for different duplexer implementation |
Huawei, HiSilicon |
R4-2209364 |
TP for 38.863 on UE Rx spurious emission requirements for satellite access |
Huawei, HiSilicon |
R4-2209401 |
Selection of UE duplexer and REFSENS for band n256 in TS 38.101-5 |
HUGHES Network Systems Ltd; Hughes/EchoStar |
R4-2209490 |
TP to TS 38.101-5 on 7.3 Reference Sensitivity |
HUGHES Network Systems Ltd, Hughes/EchoStar |
R4-2209597 |
Further discussion on NTN UE Rx RF requirements |
ZTE Corporation |
R4-2210874 |
TP to TS 38.101-5 on 7.3 Reference Sensitivity |
HUGHES Network Systems Ltd, Hughes/EchoStar |
R4-2210878 |
TP to update TS 38.101-5 clause 7.6.3 on OOBB |
Mediatek India Technology Pvt. |
9.12.6 |
RRM core requirements |
|
R4-2208497 |
Draft CR for idle mode UE meausrement capability in NTN |
LG Electronics UK |
R4-2211098 |
Draft CR for idle mode UE meausrement capability in NTN |
LG Electronics UK |
9.12.6.1 |
General |
|
R4-2207958 |
General and RRM requirements impacts |
Qualcomm Incorporated |
R4-2207994 |
draft Cat-B CR (R17) MDT in NTN |
Qualcomm Korea |
R4-2208422 |
Discussion and draft LS on measurement gaps enhancements for NTN. |
CMCC |
R4-2208470 |
Discussion on general RRM requirements in NTN |
MediaTek inc. |
R4-2209099 |
On measurement and evaluation of serving cell for NTN |
Ericsson |
R4-2209100 |
On signalling characteristics for NTN |
Ericsson |
R4-2209101 |
General requirements for NTN |
Ericsson |
R4-2209104 |
DraftCR on reselection for NTN |
Ericsson |
R4-2209212 |
Discussion on general issues for NTN RRM |
Huawei, Hisilicon |
R4-2209213 |
CR on general applicability of NTN RRM requirements |
Huawei, Hisilicon |
R4-2210177 |
On terminologies and scope in NTN RRM |
Ericsson |
R4-2210178 |
Correction to terminologies and scope in NTN RRM |
Ericsson |
R4-2210295 |
Email discussion summary: [103-e][223] NR_NTN_solutions_RRM_1 |
Moderator (Qualcomm Incorporated) |
R4-2210492 |
Email discussion summary: [103-e][223] NR_NTN_solutions_RRM_1 |
Moderator (Qualcomm Incorporated) |
R4-2210610 |
WF on NR NTN RRM requirements |
Qualcomm |
R4-2210611 |
Reply LS on measurement gap enhancements for NTN |
Intel Corporation |
R4-2211095 |
DraftCR on reselection for NTN |
Ericsson |
R4-2211097 |
Correction to terminologies and scope in NTN RRM |
Ericsson |
R4-2211099 |
CR on general applicability of NTN RRM requirements |
Huawei, Hisilicon |
R4-2211157 |
draft Cat-B CR (R17) MDT in NTN |
Qualcomm Korea |
R4-2211183 |
On signalling characteristics for NTN |
Ericsson |
R4-2211250 |
Big CR on RRM requirements for NTN |
Qualcomm |
9.12.6.2 |
GNSS-related requirements |
|
R4-2209639 |
On GNSS-Related requirements for UE operation |
Nokia, Nokia Shanghai Bell |
R4-2210296 |
Email discussion summary for [103-e][224] NR_NTN_solutions_RRM_2 |
Moderator (Xiaomi) |
R4-2210493 |
Email discussion summary for [103-e][224] NR_NTN_solutions_RRM_2 |
Moderator (Xiaomi) |
R4-2210612 |
WF on UE timing requirements and NTN RRM performance requirements |
Xiaomi |
9.12.6.3 |
Mobility requirements |
|
R4-2208054 |
DraftCR for serving cell evaluation and intra-frequency measurements of NTN UE cell reselections |
Intel Corporation |
R4-2208100 |
DraftCR on maximum interruption in paging reception for NR NTN |
Xiaomi |
R4-2208180 |
Discussion on Mobility requirements for NTN |
CATT |
R4-2208181 |
Requirements for RRC connected state mobility for NTN |
CATT |
R4-2208359 |
Discussion on mobility requirements for NTN |
OPPO |
R4-2208496 |
Discussion on NTN mobility requirements |
LG Electronics UK |
R4-2209102 |
Mobility requirements for NTN |
Ericsson |
R4-2209214 |
Discussion on mobility requirements for NTN RRM |
Huawei, Hisilicon |
R4-2209215 |
CR on IDLE mode mobility requirements for NTN |
Huawei, Hisilicon |
R4-2211090 |
DraftCR for serving cell evaluation and intra-frequency measurements of NTN UE cell reselections |
Intel Corporation |
R4-2211091 |
DraftCR on maximum interruption in paging reception for NR NTN |
Xiaomi |
R4-2211093 |
Requirements for RRC connected state mobility for NTN |
CATT |
R4-2211184 |
CR on IDLE mode mobility requirements for NTN |
Huawei, Hisilicon |
9.12.6.4 |
Timing requirements |
|
R4-2208101 |
DraftCR on UE timer accuracy for NR_NTN |
Xiaomi |
R4-2208360 |
Discussion on timing requirements for NR NTN |
OPPO |
R4-2208361 |
Draft CR to the timing requirements for NR NTN |
OPPO |
R4-2208471 |
Introduction of Timing advance requirement for NTN |
MediaTek inc. |
R4-2208653 |
Timing requirements |
Ericsson |
R4-2208995 |
Discussion on remaining issues NTN timing related requirements |
Huawei, Hisilicon |
R4-2208996 |
DraftCR on UE transmit timing requirements for NTN R17 |
Huawei, Hisilicon |
R4-2209640 |
On NTN timing requirements |
Nokia, Nokia Shanghai Bell |
R4-2211100 |
Introduction of Timing advance requirement for NTN |
MediaTek inc. |
R4-2211101 |
DraftCR on UE transmit timing requirements for NTN R17 |
Huawei, Hisilicon |
9.12.6.5 |
Measurement procedure requirements |
|
R4-2207777 |
Discussion on measurement procedure requirements for NTN |
Apple |
R4-2207959 |
Measurement procedure requirements |
Qualcomm Incorporated |
R4-2208099 |
Discussion on the remaining issues for for NTN RRM |
Xiaomi |
R4-2208102 |
DraftCR on inter-frequency measurement requirements for NR NTN |
Xiaomi |
R4-2208182 |
Discussion on Measurement procedure requirements for NTN |
CATT |
R4-2208310 |
Discussion on multiple SMTC measurement and MG in NTN |
LG Electronics Inc. |
R4-2208362 |
Discussion on measurement procedure requirements for NTN |
OPPO |
R4-2208363 |
Draft CR to general measurement requirement for NTN |
OPPO |
R4-2209103 |
Measurement requirements for NTN |
Ericsson |
R4-2209216 |
Discussion on measurement requirements for NTN |
Huawei, Hisilicon |
R4-2209217 |
CR on intra-frequency measurement requirements for NTN |
Huawei, Hisilicon |
R4-2209643 |
NTN multiple SMTC |
Nokia, Nokia Shanghai Bell |
R4-2209762 |
Draft CR on L1-RSRP measurements for Reporting in NTN |
Apple |
R4-2211092 |
DraftCR on inter-frequency measurement requirements for NR NTN |
Xiaomi |
R4-2211094 |
Draft CR to general measurement requirement for NTN |
OPPO |
R4-2211096 |
Draft CR on L1-RSRP measurements for Reporting in NTN |
Apple |
R4-2211158 |
CR on intra-frequency measurement requirements for NTN |
Huawei, Hisilicon |
9.12.7 |
RRM performance requirements |
|
R4-2207960 |
Performance requirements |
Qualcomm Incorporated |
R4-2208103 |
Discussion on the performance requirements for NTN UE timing |
Xiaomi |
R4-2208423 |
Discussion on NTN timing test cases |
CMCC |
R4-2209218 |
Discussion on measurement accuracy and TCs for NTN |
Huawei, Hisilicon |
9.12.8.1 |
General |
|
R4-2208014 |
Discussion on general issue for SAN and UE demodulation |
Ericssion |
R4-2208874 |
Discussion on general issues for NTN demodulation requirements |
Nokia, Nokia Shanghai Bell |
R4-2209874 |
Discussion on UE NTN demod general |
Huawei, HiSilicon |
R4-2210328 |
Email discussion summary for [103-e][322] NR_NTN_Demod_Part1 |
Moderator (Qualcomm Incorporated) |
R4-2210525 |
Email discussion summary for [103-e][322] NR_NTN_Demod_Part1 |
Moderator (Qualcomm Incorporated) |
R4-2210661 |
WF on NTN demodulation - general and PDSCH |
Qualcomm Incorporated |
9.12.8.2 |
Satellite Access Node demodulation requirements |
|
R4-2208085 |
View on NTN SAN demodulation requirement |
Samsung |
R4-2209681 |
TP to TS 38.108: remaining annexes for FRC (SAN demodulation requirements) |
Huawei, HiSilicon |
R4-2210329 |
Email discussion summary for [103-e][323] NR_NTN_Demod_Part2 |
Moderator (Huawei, HiSilicon) |
R4-2210526 |
Email discussion summary for [103-e][323] NR_NTN_Demod_Part2 |
Moderator (Huawei, HiSilicon) |
R4-2210662 |
WF on NTN SAN demodulation performance requirements |
Huawei, HiSilicon |
9.12.8.2.1 |
PUSCH requirements |
|
R4-2208015 |
Discussion on PUSCH requirement for SAN demodulation |
Ericssion |
R4-2208878 |
Discussion on PUSCH demodulation requirements for NTN |
Nokia, Nokia Shanghai Bell |
R4-2209877 |
Discussion on satellite NTN demod PUSCH |
Huawei, HiSilicon |
R4-2209878 |
Simulation results on satellite NTN demod PUSCH |
Huawei, HiSilicon |
9.12.8.2.2 |
PUCCH requirements |
|
R4-2208016 |
Discussion on PUCCH requirement for SAN demodulation |
Ericssion |
R4-2209879 |
Discussion on satellite NTN demod PUCCH |
Huawei, HiSilicon |
R4-2209880 |
Simulation results on satellite NTN demod PUCCH |
Huawei, HiSilicon |
9.12.8.2.3 |
PRACH requirements |
|
R4-2208017 |
Discussion on PRACH requirement for SAN demodulation |
Ericssion |
R4-2209881 |
Discussion on satellite NTN demod PRACH |
Huawei, HiSilicon |
R4-2209882 |
Simulation results on satellite NTN demod PRACH |
Huawei, HiSilicon |
9.12.8.3.1 |
PDSCH requirements |
|
R4-2207804 |
Discussion on PDSCH demod requirements for NTN |
Apple |
R4-2208880 |
Discussion on PDSCH demodulation requirements for NTN |
Nokia, Nokia Shanghai Bell |
R4-2209691 |
Discussion on PDSCH requirement for NTN |
Ericsson |
R4-2209875 |
Discussion on UE NTN demod PDSCH |
Huawei, HiSilicon |
R4-2209876 |
Simulation results on UE NTN demod PDSCH |
Huawei, HiSilicon |
R4-2210119 |
Views on NTN UE PDSCH Requirements |
Qualcomm Incorporated |
9.13 |
UE Power Saving Enhancements for NR |
|
R4-2210297 |
Email discussion summary for [103-e][225] NR_UE_pow_sav_enh |
Moderator (MediaTek inc.) |
R4-2210494 |
Email discussion summary for [103-e][225] NR_UE_pow_sav_enh |
Moderator (MediaTek inc.) |
R4-2210613 |
WF on RLM/BFD relaxation for UE Power Saving enhancements |
MediaTek Inc |
R4-2211139 |
LS to RAN2 on RLM/BFD relaxation for ePowSav |
vivo |
9.13.1 |
RRM core requirement maintenance |
|
R4-2207735 |
Power saving core maintenance |
Qualcomm, Inc. |
R4-2207737 |
Power saving criterion clarification |
Qualcomm, Inc. |
R4-2207822 |
UE measurements relaxation for RLM and/or BFD |
Apple |
R4-2208061 |
Discussions on remaining issue about UE power saving for RLM and BM |
Intel Corporation |
R4-2208095 |
Discussion about RLM/BFD measurement relaxation |
Nokia, Nokia Shanghai Bell |
R4-2208096 |
draftCR on introduction of relaxed RLM/BFD measurements |
Nokia, Nokia Shanghai Bell |
R4-2208097 |
draftCR on minimum requirements at transition for RLM/BFD relaxation |
Nokia, Nokia Shanghai Bell |
R4-2208110 |
Draft CR on RLMBFD relaxation |
Xiaomi |
R4-2208111 |
Discussion on remaining issues for RLM andor BFD relaxation |
Xiaomi |
R4-2208157 |
Discussion on remaining issues for UE Power Saving Enhancements |
CATT |
R4-2208159 |
CR on core requirements for UE power saving enhancement |
CATT |
R4-2208364 |
Discussion on RRM requirements for R17 RLMBFD relaxation |
OPPO |
R4-2208424 |
Discussion on RLM/BFD relaxation for NR power saving enhancement |
CMCC |
R4-2208730 |
RLM and RLF relaxation for UE power saving |
ZTE Corporation |
R4-2208997 |
Discussion on RRM core remaning issues for RLM/BFD relaxation |
Huawei, Hisilicon |
R4-2208998 |
DraftCR on maintaining RLM/BFD relaxation requirements |
Huawei, Hisilicon |
R4-2209497 |
Discussion on remaining issues in R17 RLM and BFD relaxation for UE power saving |
vivo |
R4-2209498 |
CR on R17 RLM and BFD relaxation for UE power saving |
vivo |
R4-2209684 |
Discussion on Rel-17 RLM/BFD measurement relaxation |
MediaTek inc. |
R4-2209685 |
CR on TS38.133 for applicability of RLM measurement relaxation |
MediaTek inc. |
R4-2209896 |
Discussions on UE power saving for RLM and BFD |
Ericsson |
R4-2209897 |
Corrections to relaxed RLM/BFD requirements |
Ericsson |
R4-2211102 |
Power saving criterion clarification |
Qualcomm, Inc. |
R4-2211103 |
CR on TS38.133 for applicability of RLM measurement relaxation |
MediaTek inc. |
R4-2211104 |
CR on core requirements for UE power saving enhancement |
CATT |
R4-2211105 |
draftCR on minimum requirements at transition for RLM/BFD relaxation |
Nokia, Nokia Shanghai Bell |
9.13.2 |
RRM performance requirements |
|
R4-2207736 |
Power saving performance |
Qualcomm, Inc. |
R4-2207823 |
UE power saving enhancement: RRM performance requirements |
Apple |
R4-2208062 |
Discussion on UE power saving test case for RLM and BM |
Intel Corporation |
R4-2208098 |
draftCR TCs of CSI-RS based BFD and LR in FR2 PSCell |
Nokia, Nokia Shanghai Bell |
R4-2208158 |
Discussion on RRM test cases for UE Power Saving Enhancements |
CATT |
R4-2208160 |
Draft CR on RRM test case for RLM relaxation based on SSB in FR2 |
CATT |
R4-2208425 |
Discussion on test cases for RLM/BFD measurement relaxation |
CMCC |
R4-2208729 |
Discussions on test cases for power saving R17 |
ZTE Corporation |
R4-2208999 |
Discussion on RRM test cases for RLM/BFD relaxation |
Huawei, Hisilicon |
R4-2209000 |
DraftCR on RLM out-of-sync tests for FR2 with CSI-RS based RLM relaxation in DRX |
Huawei, Hisilicon |
R4-2209499 |
Discussion on test cases for R17 RLM and BFD relaxation for UE power saving |
vivo |
R4-2209686 |
Discussion on Rel-17 RLM/BFD measurement relaxation test cases |
MediaTek inc. |
R4-2209687 |
CR on TS38.133 for relaxed RLM test for FR1 PSCell configured with SSB-based RLM RS in EN-DC mode (A.4.5.1.X) |
MediaTek inc. |
R4-2209688 |
CR on TS38.133 for relaxed BFD test for FR1 PSCell configured with SSB-based BFD RS in EN-DC and SA mode (A.4.5.5.X and A.6.5.5.X) |
MediaTek inc. |
R4-2209689 |
CR on TS38.133 for relaxed BFD test for FR1 PSCell configured with CSI-RS-based BFD RS in EN-DC and SA mode (A.4.5.5.X and A.6.5.5.X) |
MediaTek inc. |
R4-2209898 |
Discussions on RRM performance requirements for UE power saving |
Ericsson |
R4-2209914 |
DraftCR – Relaxed SSB-based RLM out-of-sync for FR1 PCell with DRX in SA |
Ericsson |
9.14.1 |
UE RF requirement maintenance for NR SL enhancement |
|
R4-2207963 |
TR38.785 v1.1.0 TR Update for SL enhancement in Rel-17 |
LG Electronics Deutschland |
R4-2207964 |
TR38.785 v1.2.0 TR Update for SL enhancement in Rel-17 |
LG Electronics Deutschland |
R4-2208184 |
CR for TS 38.101-1, Correction on configured transmitted power for V2X_Rel-16 |
CATT |
R4-2208185 |
CR for TS 38.101-1, Correction on configured transmitted power for V2X_Rel-17 |
CATT |
R4-2208186 |
CR for TS 38.101-1, Correction on MOP requirements for inter-band V2X con-current operation_Rel-16 |
CATT |
R4-2208187 |
CR for TS 38.101-1, Correction on MOP requirements for inter-band V2X con-current operation_Rel-17 |
CATT |
R4-2208188 |
CR for TS 38.101-3, Correction on MOP requirements for inter-band V2X con-current operation_Rel-16 |
CATT |
R4-2208189 |
CR for TS 38.101-3, Correction on MOP requirements for inter-band V2X con-current operation_Rel-17 |
CATT |
R4-2208237 |
Discussion on configured transmitted power for V2X |
CATT |
R4-2208613 |
Discussion on configured transmitted power for SL |
vivo |
R4-2208614 |
Draft CR for TS 38.101-1, Correction on configured transmitted power for SL (Rel-16) |
vivo |
R4-2208615 |
Draft CR for TS 38.101-1, Correction on configured transmitted power for SL (Rel-17) |
vivo |
R4-2209403 |
Draft CR on correction of Pemax in SL (R17) |
OPPO |
R4-2209516 |
on the remaining issue for Pemax |
Xiaomi |
R4-2209517 |
CR on Pemax definition R16 |
Xiaomi |
R4-2209518 |
CR on Pemax definition R17 |
Xiaomi |
R4-2209747 |
On Pemax for NR V2X |
Huawei, HiSilicon |
R4-2209748 |
draft CR for TS 38.101-1: correct Pemax for NR V2X (R16 Cat-F) |
Huawei, HiSilicon |
R4-2209749 |
draft CR for TS 38.101-1: correct Pemax for NR V2X (R17 Cat-A) |
Huawei, HiSilicon |
R4-2209750 |
CR to TS 38.307: SL requirements (R17) |
Huawei, HiSilicon |
R4-2210245 |
Email discussion summary for [103-e][109] NRSL_enh_maintenance_Part_1 |
Moderator (Meta) |
R4-2210445 |
Email discussion summary for [103-e][109] NRSL_enh_maintenance_Part_1 |
Moderator (Meta) |
R4-2210726 |
CR for TS 38.101-1, Correction on configured transmitted power for V2X_Rel-16 |
CATT |
R4-2210727 |
CR for TS 38.101-1, Correction on configured transmitted power for V2X_Rel-17 |
CATT |
R4-2210728 |
CR for TS 38.101-3, Correction on MOP requirements for inter-band V2X con-current operation_Rel-16 |
CATT |
R4-2210729 |
CR for TS 38.101-3, Correction on MOP requirements for inter-band V2X con-current operation_Rel-17 |
CATT |
R4-2210730 |
CR to TS 38.307: SL requirements (R17) |
Huawei, HiSilicon |
9.14.2 |
Maintenance for Intra-band con-current operation between NR SUL and NR Uu |
|
R4-2207630 |
V2X RF switching issues |
Qualcomm Incorporated |
R4-2207631 |
V2X intra-band con-current operation |
Qualcomm Incorporated |
R4-2208183 |
Reply LS on new power class capability for NR-V2X |
CATT |
R4-2208616 |
Discussion and reply LS on new power class capability for NR V2X |
vivo |
R4-2209418 |
R17 UE power class in SL intra-band concurrent operation |
OPPO |
R4-2209515 |
on the reply LS on new power class capability for NR-V2X |
Xiaomi |
R4-2209746 |
CR for TS 38.101-1: correction for NR SL con-current operation requirements (R17) |
Huawei, HiSilicon |
R4-2210246 |
Email discussion summary for [103-e][110] NRSL_enh_maintenance_Part_2 |
Moderator (CATT) |
R4-2210446 |
Email discussion summary for [103-e][110] NRSL_enh_maintenance_Part_2 |
Moderator (CATT) |
R4-2210731 |
V2X RF switching issues |
Qualcomm Incorporated |
R4-2210732 |
V2X intra-band con-current operation |
Qualcomm Incorporated |
R4-2210733 |
Reply LS on signalling of PC2 V2X intra-band con-current operation |
CATT |
9.14.3 |
Maintenance for High power UE(PC2) for SL |
|
R4-2209751 |
CR to TS 38.101-1: update of NR-V2X MPR requirements (R17) |
Huawei, HiSilicon |
R4-2210190 |
Reply LS on Signaling of PC2 V2X intra-band concurrent operation |
Qualcomm Incorporated |
9.14.4 |
RRM core requirement maintenance |
|
R4-2207739 |
SL enhancement core requirement correction |
Qualcomm, Inc. |
R4-2207874 |
Maintenance CR for RRM requirements for NR Uu and SL intra-band con-current operation |
MediaTek (Shenzhen) Inc. |
R4-2208161 |
Discussion on remaining issues for core requirements for NR SL enhancement |
CATT |
R4-2208728 |
Discussions on DRX in NR SL enhancement |
ZTE Corporation |
R4-2208817 |
CR to TS 38.133 Correction to sidelink core requirements |
vivo |
R4-2209001 |
Discussion on RRM core remaining issues for NR sidelink enhancement |
Huawei, Hisilicon |
R4-2209002 |
DraftCR on maintaining RRM core requirements for R17 NR SL |
Huawei, Hisilicon |
R4-2210298 |
Email discussion summary for [103-e][226] NR_SL_enh_RRM |
Moderator (LG Electronics) |
R4-2210495 |
Email discussion summary for [103-e][226] NR_SL_enh_RRM |
Moderator (LG Electronics) |
R4-2210614 |
WF on NR SL enhancements RRM requirements |
LG Electronics |
R4-2211106 |
SL enhancement core requirement correction |
Qualcomm, Inc. |
R4-2211107 |
Maintenance CR for RRM requirements for NR Uu and SL intra-band con-current operation |
MediaTek (Shenzhen) Inc. |
R4-2211108 |
CR to TS 38.133 Correction to sidelink core requirements |
vivo |
R4-2211109 |
CR on maintaining RRM core requirements for R17 NR SL |
Huawei, Hisilicon |
9.14.5 |
RRM performance requirements |
|
R4-2207738 |
SL enhancement resource selection test |
Qualcomm, Inc. |
R4-2207740 |
SL enhancement resource selection test configuration and RRM requirement correction |
Qualcomm, Inc. |
R4-2208582 |
draft CR on Test for Interruption to WAN at transitions during SL-DRX for Asynchronized case |
LG Electronics |
R4-2208818 |
Draft CR to TS 38.133: Introduction of test cases for Selection/Reselection of V2X SyncRef Source under SL-DRX |
vivo |
R4-2208819 |
Discussion on performance requirements for sidelink enhancement |
vivo |
R4-2209003 |
Discussion on test setup for initiation/cease SLSS transmisions in SL-DRX mode |
Huawei, Hisilicon |
R4-2209004 |
DraftCR on initiation/cease SLSS transmisions in SL-DRX mode |
Huawei, Hisilicon |
R4-2211110 |
draft CR on Test for Interruption to WAN at transitions during SL-DRX for Asynchronized case |
LG Electronics |
R4-2211111 |
Draft CR to TS 38.133: Introduction of test cases for Selection/Reselection of V2X SyncRef Source under SL-DRX |
vivo |
R4-2211112 |
DraftCR on initiation/cease SLSS transmisions in SL-DRX mode |
Huawei, Hisilicon |
9.14.6 |
Demodulation performance requirements |
|
R4-2208318 |
Discussion on test cases for SL enhancement demodulation requirements |
LG Electronics Inc. |
R4-2209849 |
Discussion on demodulation requirements for NR sidelink enhancements |
Huawei, HiSilicon |
R4-2210330 |
Email discussion summary for [103-e][324] NR_SL_enh_Demod |
Moderator (LG Electronics) |
R4-2210527 |
Email discussion summary for [103-e][324] NR_SL_enh_Demod |
Moderator (LG Electronics) |
R4-2210663 |
WF on SL enhancement demodulation |
LG Electronics |
9.15.1 |
General |
|
R4-2208045 |
UE features for NR ext. to 71GHz WI |
Intel Corporation |
R4-2208143 |
Draft reply LS on the minimum guard period between two SRS resources for antenna switching |
CATT |
R4-2208541 |
Draft CR to TS 38.104: Addition of support for band n264 for licensed operation within 66000 to 71000 MHz |
Ericsson |
R4-2208617 |
Draft CR for TS 38.101-2: Introduction of system parameters for FR2-2 |
vivo |
R4-2208763 |
Draft reply LS on the minimum guard period between two SRS resources for antenna switching |
Huawei, HiSilicon |
R4-2209322 |
Multi-band relaxation requirement for band n263 |
Apple |
R4-2209509 |
further discussion and draft reply LS on minimum guard symbol of SRS |
Xiaomi |
R4-2209716 |
UE features for NR in 52.6 GHz - 71 GHz |
Nokia, Nokia Shanghai Bell |
R4-2210080 |
draft CR 38.101-3 on FR2-2 DC/CA with FR1 anchor |
Ericsson |
R4-2210266 |
Email discussion summary for [103-e][131] NR_ext_to_71GHz_Part_1 |
Moderator (Intel Corporation) |
R4-2210463 |
Email discussion summary for [103-e][131] NR_ext_to_71GHz_Part_1 |
Moderator (Intel Corporation) |
R4-2210577 |
WF on system parameters for NR extension to 71GHz |
Intel Corporation |
R4-2210785 |
Draft reply LS on the minimum guard period between two SRS resources for antenna switching |
CATT |
R4-2210787 |
Draft CR to TS 38.104: Addition of support for band n264 for licensed operation within 66000 to 71000 MHz |
Ericsson |
R4-2210788 |
Draft CR for TS 38.101-2: Introduction of system parameters for FR2-2 |
vivo |
R4-2211268 |
Big CR on extending NR to 71GHz for TS 38.101-2 |
Intel |
R4-2211269 |
Big CR on extending NR to 71GHz for TS 38.104 |
Intel |
9.15.2 |
Operation bands and system parameters (channelization, raster, CBW, etc) |
|
R4-2207780 |
Remaining issues on system parameters for NR operation in 52.6GHz - 71GHz |
Apple |
R4-2208046 |
Further views on channelization for FR2-2 |
Intel Corporation |
R4-2208047 |
Draft CR to introduce the channel and sync rasters of band n263 (option 1) |
Intel Corporation |
R4-2208048 |
Draft CR to introduce the channel and sync rasters of band n263 (option 1) |
Intel Corporation |
R4-2208479 |
System parameters for a NR band in the range 52.6GHz – 71GHz |
Nokia, Nokia Shanghai Bell |
R4-2208540 |
Draft CR to TS 38.104: Addition of FR2-2definition in sucblause 5.1, n263 in subalcuse 5.2 and transmission bandwidth information in subclause 5.3 |
Ericsson |
R4-2208618 |
Further discussion on channel raster and sync raster for NR extending to 71GHz |
vivo |
R4-2208649 |
60GHz channel and synchronization raster |
LG Electronics Finland |
R4-2209139 |
52.6-71 GHz System Parameters |
Ericsson |
R4-2209682 |
Draft CR to TS 38.101-2: Channel arrangement and channel bandwidths for 66-71 GHz |
Huawei, HiSilicon |
R4-2209683 |
Draft CR to TS 38.104: Channel arrangement and channel bandwidths for 66-71 GHz |
Huawei, HiSilicon |
R4-2210117 |
Draft CR to introduce the channel and sync rasters of band n263 (option 2) |
Intel Corporation |
R4-2210118 |
Draft CR to introduce the channel and sync rasters of band n263 (option2) |
Intel Corporation |
R4-2210188 |
60GHz UE bandwidths |
Qualcomm Incorporated |
R4-2210786 |
Draft CR to TS 38.104: Addition of FR2-2definition in sucblause 5.1, n263 in subalcuse 5.2 and transmission bandwidth information in subclause 5.3 |
Ericsson |
R4-2210789 |
Draft CR to introduce the channel and sync rasters of band n263 (option 2) |
Intel Corporation |
R4-2210790 |
Draft CR to introduce the channel and sync rasters of band n263 (option2) |
Intel Corporation |
9.15.3 |
UE RF requirements |
|
R4-2210267 |
Email discussion summary for [103-e][132] NR_ext_to_71GHz_Part_2 |
Moderator (Qualcomm) |
R4-2210464 |
Email discussion summary for [103-e][132] NR_ext_to_71GHz_Part_2 |
Moderator (Qualcomm) |
R4-2210578 |
WF on 60 GHz UE Requirements |
Qualcomm Incorporated |
9.15.3.1 |
TX requirements |
|
R4-2207696 |
On remaining Tx issues for band n263 |
Apple |
R4-2207697 |
Draft CR to 38.101-2 on band n263 Tx aspects |
Apple |
R4-2208049 |
UE Tx requirements for FR2-2 - remaining issues |
Intel Corporation |
R4-2208226 |
Discussion on FFT sizes for 52 6-71GHz |
CATT |
R4-2208619 |
Discussion on remaining Tx RF requirements for FR2-2 |
vivo |
R4-2208647 |
Discussion on open specification items for Tx RF requirements |
LG Electronics Finland |
R4-2208754 |
Upper limit on configured maximum power for 57-71 GHz |
Ericsson |
R4-2208759 |
On n263 associated band specific Tx requirements |
Huawei, HiSilicon |
R4-2208760 |
Draft CR for n263 RF Tx requirements |
Huawei, HiSilicon |
R4-2208781 |
draft CR on open specification for PC2 in FR2-2 |
LG Electronics Finland |
R4-2209507 |
on the UE TX requirement |
Xiaomi |
R4-2209510 |
draftCR on the UE TX requirement for band n263 |
Xiaomi |
R4-2209717 |
On UE Tx RF aspects for FR2-2 |
Nokia, Nokia Shanghai Bell |
R4-2210166 |
60 GHz UE TX |
Qualcomm Incorporated |
R4-2210350 |
On UE Tx RF aspects for FR2-2 |
Nokia, Nokia Shanghai Bell |
R4-2210433 |
60 GHz UE TX |
Qualcomm Incorporated |
R4-2211196 |
Draft CR to 38.101-2 on band n263 Tx aspects |
Apple |
9.15.3.2 |
RX requirements |
|
R4-2208620 |
Discussion on remaining Rx RF requirements for FR2-2 |
vivo |
R4-2208761 |
On n263 associated band specific Rx requirements |
Huawei, HiSilicon |
R4-2208762 |
Draft CR for n263 RF Rx requirements |
Huawei, HiSilicon |
R4-2209323 |
Rx requirement for band n263 |
Apple |
R4-2209508 |
on the UE RX requirement |
Xiaomi |
R4-2209511 |
draftCR on the UE RX requirement for band n263 |
Xiaomi |
R4-2209718 |
On UE Rx RF aspects for FR2-2 |
Nokia, Nokia Shanghai Bell |
R4-2211161 |
draftCR on the UE RX requirement for band n263 |
Xiaomi |
9.15.4 |
BS RF requirements |
|
R4-2210317 |
Email discussion summary for [103-e][311] NR_exto71GHz_BSRF |
Moderator (Nokia) |
R4-2210514 |
Email discussion summary for [103-e][311] NR_exto71GHz_BSRF |
Moderator (Nokia) |
R4-2210637 |
WF on BS RF requirements for FR2-2 |
Nokia, Nokia Shanghai Bell |
R4-2210638 |
WF on BS RF conformance testing for FR2-2 |
ZTE |
R4-2210639 |
Draft CR to 38.104 on BS RF Rx requirements in clauses 10-10.5 |
CATT |
R4-2210640 |
Draft CR to 38.104 on FRC Annexes |
Huawei |
R4-2210641 |
Big CR to 38.104 for Rel-17 NR extension up to 71 GHz introduction |
Nokia, Nokia Shanghai Bell |
9.15.4.1 |
TX requirements |
|
R4-2207923 |
Proposals on BS transmitter requirements for extending current NR operation to 71 GHz |
Nokia, Nokia Shanghai Bell |
R4-2208227 |
Discussion on BS TX RF requirements for 52 6-71GHz |
CATT |
R4-2208537 |
On BS RF transmitter requirements for the frequency range 52.6 to 71.0 GHz |
Ericsson |
R4-2208539 |
Draft CR to TS 38.104: Addition of EVM window length for 480 kHz and 960 kHz SCS in Annex C.5 |
Ericsson |
R4-2209586 |
Further discussion on BS Tx requirements for 52.6-71GHz |
ZTE Corporation |
R4-2209587 |
Draft CR to TS 38.104: intra-band non-contiguous CA TAE requirement and EVM measurement window length |
ZTE Corporation |
R4-2210879 |
Draft CR to TS 38.104: Addition of EVM window length for 480 kHz and 960 kHz SCS in Annex C.5 |
Ericsson |
R4-2210880 |
Draft CR to TS 38.104: intra-band non-contiguous CA TAE and ACLR for FR2-2 |
ZTE Corporation |
9.15.4.2 |
RX requirements |
|
R4-2207924 |
Proposals on BS receiver requirements for extending current NR operation to 71 GHz |
Nokia, Nokia Shanghai Bell |
R4-2208228 |
Discussion on BS RX RF requirements for 52 6-71GHz |
CATT |
R4-2208538 |
On BS RF receiver requirements for the frequency range 52.6 to 71.0 GHz |
Ericsson |
R4-2208570 |
View on remaining issues for 71GHz BS RX requirements |
Samsung |
R4-2209588 |
Further discussion on BS Rx requirements for 52.6-71GHz |
ZTE Corporation |
R4-2209589 |
Draft CR for TS 38.104 on introduction of BS RF Rx requirements for 57-71GHz in section 10.6 – 10.9 |
ZTE Corporation |
R4-2210881 |
Draft CR for TS 38.104 on introduction of BS RF Rx requirements for 57-71GHz in section 10.6 – 10.9 |
ZTE Corporation |
9.15.5.1 |
General |
|
R4-2208542 |
On general aspects related to FR2-2 base station OTA conformance testing |
Ericsson |
R4-2209141 |
about FR2-2 BS conformance test system |
Keysight Technologies UK Ltd |
R4-2209590 |
Discussion on BS conformance testing for 52.6-71GHz |
ZTE Corporation |
R4-2209719 |
Measurement uncertainty considerations for NR in 52.6GHz – 71GHz |
Nokia, Nokia Shanghai Bell |
9.15.5.2 |
Transmitter characteristics |
|
R4-2207925 |
Proposals on BS transmitter conformance testing for extending current NR operation to 71 GHz |
Nokia, Nokia Shanghai Bell |
R4-2208229 |
Discussion on BS RFtransmitter characteristics conformance testing |
CATT |
R4-2208543 |
BS transmitter conformance test specification impact overview |
Ericsson |
R4-2209142 |
about FR2-2 BS conformance test, EVM measurement and TM length |
Keysight Technologies UK Ltd |
9.15.5.3 |
Receiver characteristics |
|
R4-2207926 |
Proposals on BS receiver conformance testing for extending current NR operation to 71 GHz |
Nokia, Nokia Shanghai Bell |
R4-2208230 |
Discussion on BS RFreceiver characteristics conformance testing |
CATT |
R4-2208544 |
BS receiver conformance test specification impact overview |
Ericsson |
9.15.8 |
RRM core requirements |
|
R4-2210285 |
Email discussion summary for [103-e][213] NR_ext_to_71GHz_RRM_2 |
Moderator (Intel Corporation) |
R4-2210482 |
Email discussion summary for [103-e][213] NR_ext_to_71GHz_RRM_2 |
Moderator (Intel Corporation) |
R4-2210591 |
WF on LBT impacts on RRM requirements for FR2-2 |
Intel Corporation |
R4-2211171 |
LS on CCA configurations of neighbour cells |
Nokia |
9.15.8.1 |
General |
|
R4-2207783 |
On Rx beam sweeping scaling factor |
Apple |
R4-2208144 |
Further discussion on General RRM requirements for extension to 71GHz |
CATT |
R4-2208308 |
Discussion on general RRM measurement requirements for extension to 71GHz |
LG Electronics Inc. |
R4-2208732 |
Discussions on the Rx beam sweeping factor |
ZTE Corporation |
R4-2208809 |
Remian issues on RRM impacts for extending NR operation to 71GHz |
vivo |
R4-2208811 |
Draft CR - Introduction of scheduling restriction requirements in FR2-2 |
vivo |
R4-2208946 |
Discussion on general requirements for extending NR operation to 71GHz |
Huawei, Hisilicon |
R4-2209050 |
Draft CR to TS 38.133 Corrections on scheduling availability in FR2-2 |
Nokia, Nokia Shanghai Bell |
R4-2209094 |
On inter_frequency requriements with LBT |
Ericsson |
R4-2209095 |
General RRM requirements for extending NR operation to 71GHz |
Ericsson |
R4-2209384 |
Discussion on general RRM requirements for extension to 71 GHz |
Nokia, Nokia Shanghai Bell |
R4-2210223 |
Measurement procedures for FR2-2 |
Qualcomm Incorporated |
R4-2210284 |
Email discussion summary for [103-e][212] NR_ext_to_71GHz_RRM_1 |
Moderator (Qualcomm) |
R4-2210481 |
Email discussion summary for [103-e][212] NR_ext_to_71GHz_RRM_1 |
Moderator (Qualcomm) |
R4-2210590 |
WF on NR extension to 71 GHz RRM requirements (Part 1) |
Qualcomm |
R4-2211036 |
On inter_frequency requriements with LBT |
Ericsson |
R4-2211248 |
Big CR on extending NR to 71GHz for TS38.133 |
Intel Corporation |
9.15.8.2 |
Timing requirements |
|
R4-2207781 |
UE transmit timing for NR operation in 52.6GHz - 71GHz |
Apple |
R4-2207782 |
Draft CR on UE transmit timing for NR operation in 52.6GHz - 71GHz |
Apple |
R4-2208145 |
Further discussion on RRM timing requirements for higher SCS |
CATT |
R4-2208650 |
UE timing requirements |
Ericsson |
R4-2208810 |
Remian issues on timing requirements for 52.6-71GHz |
vivo |
R4-2208812 |
Draft CR - Introduction of deriveSSB-IndexFromCell tolerance requirements in FR2-2 |
vivo |
R4-2208947 |
Discussion on timing requirements for extending NR operation to 71GHz |
Huawei, Hisilicon |
R4-2209385 |
Discussion on RRM timing requirements for extension to 71 GHz |
Nokia, Nokia Shanghai Bell |
R4-2209386 |
Draft CR adding timing requirements for FR2-2 |
Nokia, Nokia Shanghai Bell |
R4-2211031 |
Draft CR adding timing requirements for FR2-2 |
Nokia, Nokia Shanghai Bell |
R4-2211032 |
Draft CR on UE transmit timing for NR operation in 52.6GHz - 71GHz |
Apple |
9.15.8.6 |
LBT impacts on RRM requirements |
|
R4-2207784 |
LBT impacts on RRM requirements for NR operation in 52.6GHz - 71GHz |
Apple |
R4-2208056 |
Discussion on LBT impacts on RRM requirements for NR 52.6 – 71 GHz |
Intel Corporation |
R4-2208057 |
DraftCR for FR2-2 LBT support in RRC_IDLE, RRC_INACTIVE and RRC_CONNECTED state mobility requirements |
Intel Corporation |
R4-2208472 |
Discussion on LBT impacts on RRM requirements in FR2-2 |
MediaTek inc. |
R4-2208948 |
Discussion on LBT impacts for extending NR operation to 71GHz |
Huawei, Hisilicon |
R4-2208949 |
Draft CR on RLM and Link recovery procedures for unlicensed operation in FR2-2 |
Huawei, Hisilicon |
R4-2209051 |
Draft CR to TS 38.133 Intra-frequency measurement requirements with CCA in FR2-2 |
Nokia, Nokia Shanghai Bell |
R4-2209053 |
Discussion on RRM requirements with CCA in FR2-2 |
Nokia, Nokia Shanghai Bell |
R4-2209096 |
LBT impacts on RRM requirements for extending NR operation to 71GHz |
Ericsson |
R4-2210232 |
DraftCR for FR2-2 LBT support in L1-RSRP measurements for reporting |
Qualcomm Incorporated |
R4-2211033 |
DraftCR for FR2-2 LBT support in RRC_IDLE, RRC_INACTIVE and RRC_CONNECTED state mobility requirements |
Intel Corporation |
R4-2211034 |
Draft CR on RLM and Link recovery procedures for unlicensed operation in FR2-2 |
Huawei, Hisilicon |
R4-2211035 |
Draft CR to TS 38.133 Intra-frequency measurement requirements with CCA in FR2-2 |
Nokia, Nokia Shanghai Bell |
R4-2211180 |
DraftCR for FR2-2 LBT support in L1-RSRP measurements for reporting |
Qualcomm Incorporated |
9.15.9 |
RRM performance requirements |
|
R4-2208146 |
Test case list for NR extension to 71 GHz RRM requirements |
CATT |
R4-2208731 |
Views on the statistical tests for Te requirements |
ZTE Corporation |
R4-2208813 |
Discussion on performance requirements for 52.6-71GHz |
vivo |
R4-2208950 |
Discussion on performance requirements for extending NR operation to 71GHz |
Huawei, Hisilicon |
R4-2209052 |
Discussion on RRM performance in FR2-2 |
Nokia, Nokia Shanghai Bell |
R4-2210224 |
FR2-2 RRM Performance Work Plan |
Qualcomm Incorporated |
9.15.10 |
Demodulation and CSI requirements |
|
R4-2210331 |
Email discussion summary for [103-e][325] NR_exto71GHz_Demod_Part1 |
Moderator (Intel Corporation) |
R4-2210528 |
Email discussion summary for [103-e][325] NR_exto71GHz_Demod_Part1 |
Moderator (Intel Corporation) |
R4-2210664 |
WF on general and BS aspects for FR2-2 demodulation requirements |
Intel Corporation |
9.15.10.1 |
General |
|
R4-2208018 |
Discussion on general issue for NR extended to 71GHz demodulation requirements |
Ericssion |
R4-2209387 |
Draft CR - definition of FR2-2 |
Nokia, Nokia Shanghai Bell |
R4-2209388 |
Discussion on general aspects of demodulation requirements for the extension to 71 GHz |
Nokia, Nokia Shanghai Bell |
9.15.10.2 |
UE Demodulation and CSI requirements |
|
R4-2207805 |
Discussion on UE demod and CSI reporting requirements for FR2-2 |
Apple |
R4-2209778 |
Initial Simulation results for UE demod requirements for FR2-2 |
Apple |
R4-2210332 |
Email discussion summary for [103-e][326] NR_exto71GHz_Demod_Part2 |
Moderator (Qualcomm Incorporated) |
R4-2210351 |
Initial Simulation results for UE demod requirements for FR2-2 |
Apple |
R4-2210529 |
Email discussion summary for [103-e][326] NR_exto71GHz_Demod_Part2 |
Moderator (Qualcomm Incorporated) |
R4-2210665 |
WF on UE demodulation performance requirements definition for 52.6 - 71 GHz |
Qualcomm Incorporated |
9.15.10.2.1 |
PDSCH requirements |
|
R4-2208262 |
On PDSCH requirements for the extention to 71GHz |
Nokia, Nokia Shanghai Bell |
R4-2208324 |
The remaining issues of the PDSCH requirements in 52.6 – 71 GHz band |
Ericsson |
R4-2208325 |
Simulation results for PDSCH demodulation in 52.6 GHz – 71 GHz band |
Ericsson |
R4-2208331 |
draft CR on PDSCH requirements for 52.6 - 71 GHz band |
Ericsson |
R4-2209737 |
PDSCH simulation results for the extension to 71 GHz |
Nokia, Nokia Shanghai Bell |
R4-2209842 |
Discussion on PDSCH requirements for FR2-2 |
Huawei, HiSilicon |
9.15.10.2.2 |
PDCCH/PBCH requirements |
|
R4-2208263 |
On PDCCH and PBCH requirements for the extention to 71GHz |
Nokia, Nokia Shanghai Bell |
R4-2208264 |
draftCR to 38101-4: NR PDCCH requirements for the extention to 71GHz |
Nokia, Nokia Shanghai Bell |
R4-2208326 |
On the PDCCH and PBCH requirements in 52.6 GHz – 71 GHz band |
Ericsson |
R4-2208327 |
Simulation results for PDCCH and PBCH demodulation in FR2-2 |
Ericsson |
R4-2209843 |
Discussion on PDCCH/PBCH requirements |
Huawei, HiSilicon |
9.15.10.2.3 |
SDR requirements |
|
R4-2208328 |
SDR requirements in 52.6 – 71 GHz band |
Ericsson |
R4-2208329 |
Simulation results for SDR requirements in 52.6 – 71 GHz band |
Ericsson |
R4-2208332 |
draft CR on SDR requirements for 52.6 - 71 GHz band |
Ericsson |
R4-2209844 |
Discussion on SDR requirements for FR2-2 |
Huawei, HiSilicon |
9.15.10.2.4 |
CSI reporting requirements |
|
R4-2208330 |
CSI reporting requirements in 52.6 GHz – 71 GHz band |
Ericsson |
R4-2209845 |
Discussion on CSI reporting requirements for FR2_2 |
Huawei, HiSilicon |
9.15.10.3 |
BS demodulation requirements |
|
R4-2208084 |
View on BS demodulation requirement for NR extended to 71GHz |
Samsung |
9.15.10.3.1 |
PUSCH requirements |
|
R4-2208019 |
Discussion on PUSCH demodulation requirements for NR extended to 71GHz |
Ericssion |
R4-2208022 |
Simulation results on PUSCH demodulation requirements for NR extended to 71GHz |
Ericssion |
R4-2209389 |
Discussion on PUSCH demodulation requirements for the extension to 71 GHz |
Nokia, Nokia Shanghai Bell |
R4-2209390 |
PUSCH simulation results for the extension to 71 GHz |
Nokia, Nokia Shanghai Bell |
R4-2209397 |
Big CR Introduction fo FR2-2 BS Radiated demodulation requirements for TS 38.141-2 |
Nokia, Nokia Shanghai Bell |
R4-2209846 |
Discussion on PUSCH requirements for FR2-2 |
Huawei, HiSilicon |
9.15.10.3.2 |
PUCCH requirements |
|
R4-2208020 |
Discussion on PUCCH demodulation requirements for NR extended to 71GHz |
Ericssion |
R4-2208023 |
Simulation results on PUCCH demodulation requirements for NR extended to 71GHz |
Ericssion |
R4-2209391 |
Discussion on PUCCH demodulation requirements for the extension to 71 GHz |
Nokia, Nokia Shanghai Bell |
R4-2209392 |
PUCCH simulation results for the extension to 71 GHz |
Nokia, Nokia Shanghai Bell |
R4-2209847 |
Discussion on PUCCH requirements for FR2-2 |
Huawei, HiSilicon |
9.15.10.3.3 |
PRACH requirements |
|
R4-2208021 |
Discussion on PRACH demodulation requirements for NR extended to 71GHz |
Ericssion |
R4-2209393 |
Discussion on PRACH demodulation requirements for the extension to 71 GHz |
Nokia, Nokia Shanghai Bell |
R4-2209394 |
PRACH simulation results for the extension to 71 GHz |
Nokia, Nokia Shanghai Bell |
R4-2209395 |
Draft CR 38.104: PRACH requirements for FR2-2 |
Nokia, Nokia Shanghai Bell |
R4-2209396 |
Draft CR 38.141-2: PRACH requirements for FR2-2 |
Nokia, Nokia Shanghai Bell |
R4-2209848 |
Discussion on PRACH requirements for FR2-2 |
Huawei, HiSilicon |
9.16.1 |
General |
|
R4-2208571 |
Updated work plan for eIAB performance part |
Samsung |
R4-2209806 |
CR to TS 38.174 with bracket removal for timing error between IAB-DU and IAB-MT |
Nokia, Nokia Shanghai Bell |
R4-2210318 |
Email discussion summary for [103-e][312] NR_eIAB_RF |
Moderator (Samsung) |
R4-2210515 |
Email discussion summary for [103-e][312] NR_eIAB_RF |
Moderator (Samsung) |
R4-2210642 |
LS on range of power control parameters for eIAB |
Samsung |
R4-2210643 |
WF on conformance testing for eIAB |
Samsung |
9.16.2 |
RF requirements maintenance |
|
R4-2208505 |
Discussion on timing issues for simultaneous operation of IAB |
ZTE Corporation |
R4-2208506 |
Reply LS to Reply LS on power control parameters for eIAB |
ZTE Corporation |
R4-2208572 |
Draft CR for eIAB clean up |
Samsung |
R4-2208573 |
Discussion on reply LS for range of power control parameters |
Samsung |
R4-2209462 |
IAB MT /DU Case-6 timing |
Ericsson |
R4-2209463 |
LS response on range of power control parameters for eIAB |
Ericsson |
R4-2209464 |
CR on case-6 timing for eIAB_RF |
Ericsson |
R4-2209720 |
Discussion on range of power control parameters |
Nokia, Nokia Shanghai Bell |
9.16.3 |
RF conformance testing |
|
R4-2208507 |
Discussion on conformance test of IAB |
ZTE Corporation |
R4-2208574 |
Discussion on RF conformance testing for eIAB |
Samsung |
R4-2209465 |
eIAB conformance test |
Ericsson |
R4-2209466 |
CR on Test configuration for eIAB conformance testing 38.176-1 |
Ericsson |
R4-2209467 |
CR on Test configuration for eIAB conformance testing 38.176-2 |
Ericsson |
R4-2209807 |
On eIAB simultaneous operation testing |
Nokia, Nokia Shanghai Bell |
R4-2210029 |
eIAB testing case#6 intra node TAE |
Huawei |
R4-2211200 |
CR on Test configuration for eIAB conformance testing 38.176-1 |
Ericsson |
R4-2211201 |
CR on Test configuration for eIAB conformance testing 38.176-2 |
Ericsson |
9.16.4 |
RRM core requirements maintenance |
|
R4-2210299 |
Email discussion summary for [103-e][227] NR_IAB_enh_RRM |
Moderator (ZTE Corporation) |
R4-2210496 |
Email discussion summary for [103-e][227] NR_IAB_enh_RRM |
Moderator (ZTE Corporation) |
R4-2210615 |
WF on IAB enhancement RRM (Perf Part) |
ZTE Corporation |
9.16.5 |
RRM performance requirements |
|
R4-2207905 |
On eIAB RRM Performance Requirements |
Nokia, Nokia Shanghai Bell |
R4-2208951 |
Discussion on performance requirements for eIAB |
Huawei, Hisilicon |
R4-2210174 |
Impact on RRM performance requirements for enhanced IAB |
Ericsson |
9.16.6 |
Demodulation requirements |
|
R4-2210890 |
[dCR] Maintenance for IAB-MT performance requirement R16 |
ZTE Corporation |
R4-2210891 |
[dCR] Maintenance for IAB-MT performance requirement R17 Cat A |
ZTE Corporation |
9.17.1 |
UE RF requirement maintenance |
|
R4-2207861 |
Updated summary of RF agreements for NR coverage enhancements WI |
China Telecom |
R4-2209163 |
On remaining issues for NR coverage enhancements |
Huawei, HiSilicon |
R4-2209164 |
CR on clarification for DMRS bundling RF requirements for SUL in TS 38.101-1 |
Huawei, HiSilicon |
R4-2209165 |
CR on UE RF requirements for DMRS bundling in TS 38.101-1 |
Huawei, HiSilicon |
R4-2210081 |
DMRS bundling – UE RF “maintenance” aspects |
MediaTek (Chengdu) Inc. |
R4-2210247 |
Email discussion summary for [103-e][112] NR_cov_enh_maintenance |
Moderator (China Telecom) |
R4-2210447 |
Email discussion summary for [103-e][112] NR_cov_enh_maintenance |
Moderator (China Telecom) |
R4-2210548 |
WF on DMRS bundling for CA, SUL and FR2-2 |
China Telecom |
R4-2210549 |
Reply LS to RAN1/RAN2 on DMRS bundling |
MediaTek |
R4-2210550 |
LS to RAN5 on measurement of phase continuity requirements for DMRS bundling |
Ericsson |
R4-2210551 |
draft CR to TS 38.101-1: Maintenance of phase continuity requirements for DMRS bundling |
MediaTek |
R4-2210734 |
Updated summary of RF agreements for NR coverage enhancements WI |
China Telecom |
R4-2210735 |
CR on clarification for DMRS bundling RF requirements for SUL in TS 38.101-1 |
Huawei, HiSilicon |
R4-2211126 |
draft CR to TS 38.101-2: Maintenance of phase continuity requirements for DMRS bundling |
MediaTek |
R4-2211225 |
Reply LS to RAN1/RAN2 on DMRS bundling |
MediaTek |
9.17.1.1 |
Phase continuity core requirement maintenance |
|
R4-2207657 |
Discussion on additional requirements for DMRS bundling |
Qualcomm Incorporated, China Telecom, T-Mobile USA, Verizon, CMCC |
R4-2207658 |
Handling of UL CA for DMRS bundling |
Qualcomm Incorporated |
R4-2207659 |
CR 38.101-1 DMRS for CA |
Qualcomm Incorporated, China Telecom, T-Mobile USA, CMCC, Nokia |
R4-2207695 |
On coverage enhancement combined with UL MIMO |
Apple |
R4-2207862 |
Maintenance of phase continuity requirements for DMRS bundling |
China Telecom |
R4-2207864 |
Reply LS on modulation order for DMRS bundling |
China Telecom |
R4-2209456 |
remaining issue related to DMRS bundling requirement |
Ericsson |
R4-2209458 |
CR on DMRS bundling phase offset Requirment FR1 |
Ericsson |
R4-2209459 |
CR on DMRS bundling phase offset Requirment FR2 |
Ericsson |
R4-2210215 |
Handling of UL CA for DMRS bundling |
Qualcomm Incorporated |
R4-2210736 |
CR 38.101-1 DMRS for CA |
Qualcomm Incorporated, China Telecom, T-Mobile USA, CMCC, Nokia |
R4-2211173 |
DMRS bundling for CA and DC |
Qualcomm |
9.17.1.2 |
Issues for measurement and test setup |
|
R4-2207863 |
On measurement of phase continuity requirements for DMRS bundling |
China Telecom |
R4-2209157 |
Phase difference measurement for DMRS bundling |
Anritsu Limited |
R4-2209158 |
Draft CR for new additions to Annex F9 related to the FR1 DMRS bundling requirements |
Anritsu Limited |
R4-2209159 |
Draft CR for new additions to Annex F9 related to the FR2 DMRS bundling requirements |
Anritsu Limited |
R4-2209457 |
On measurement of the TX coherent transmission |
Ericsson |
R4-2209460 |
CR on DMRS bundling phase offset measurement FR1 |
Ericsson |
R4-2209461 |
CR on DMRS bundling phase offset measurement FR2 |
Ericsson |
R4-2210344 |
Draft CR for new additions to Annex F9 related to the FR1 DMRS bundling requirements |
Anritsu Limited |
R4-2210345 |
Draft CR for new additions to Annex F8 related to the FR2 DMRS bundling requirements |
Anritsu Limited |
R4-2210737 |
CR on DMRS bundling phase offset measurement FR1 |
Ericsson, Anritsu Limited |
R4-2210738 |
CR on DMRS bundling phase offset measurement FR2 |
Ericsson, Anritsu Limited |
9.17.2 |
BS demodulation requirements |
|
R4-2210333 |
Email discussion summary for [103-e][327] NR_cov_enh_Demod |
Moderator (China Telecom) |
R4-2210530 |
Email discussion summary for [103-e][327] NR_cov_enh_Demod |
Moderator (China Telecom) |
R4-2210666 |
WF on PUSCH demodulation performance of Rel-17 NR coverage enhancement |
China Telecom |
R4-2210667 |
WF on PUCCH demodulation performance of Rel-17 NR coverage enhancement |
Nokia |
R4-2210668 |
Simulation results collection for coverage enhancement for PUSCH |
China Telecom |
9.17.2.1 |
PUSCH requirements |
|
R4-2207742 |
PUSCH demodulation performance of Rel-17 NR coverage enhancements |
Nokia, Nokia Shanghai Bell |
R4-2208009 |
PUSCH demodulation performance of Rel-17 NR coverage enhancements: simulation results |
Nokia, Nokia Shanghai Bell |
R4-2208010 |
Discussion on PUSCH demodulation for NR coverage enhancement |
Ericssion |
R4-2208011 |
Simulation results for PUSCH demodulation for NR coverage enhancement |
Ericssion |
R4-2208082 |
View on PUSCH demodulation requirement for Rel-17 coverage enhancement |
Samsung |
R4-2209407 |
On BS PUSCH demodulation requirements for NR coverage enhancements |
China Telecom |
R4-2209883 |
Discussion on BS coverage enhancement demod PUSCH |
Huawei, HiSilicon |
R4-2209884 |
Simulation results on BS coverage enhancement demod PUSCH |
Huawei, HiSilicon |
9.17.2.2 |
PUCCH requirements |
|
R4-2207743 |
PUCCH demodulation performance of Rel-17 NR coverage enhancements |
Nokia, Nokia Shanghai Bell |
R4-2208012 |
Discussion on PUCCH demodulation for NR coverage enhancement |
Ericssion |
R4-2208013 |
Simulation results for PUCCH demodulation for NR coverage enhancement |
Ericssion |
R4-2208083 |
View on PUCCH demodulation requirement for Rel-17 coverage enhancement |
Samsung |
R4-2209406 |
On BS PUCCH demodulation requirements for NR coverage enhancements |
China Telecom |
R4-2209885 |
Discussion on BS coverage enhancement demod PUCCH |
Huawei, HiSilicon |
R4-2209886 |
Simulation results on BS coverage enhancement demod PUCCH |
Huawei, HiSilicon |
9.18.1 |
UE RF requirement maintenance |
|
R4-2210248 |
Email discussion summary for [103-e][113] NR_feMIMO_maintenance |
Moderator (Samsung) |
R4-2210448 |
Email discussion summary for [103-e][113] NR_feMIMO_maintenance |
Moderator (Samsung) |
R4-2210552 |
WF on FeMIMO maintenance |
Samsung |
R4-2211174 |
LS on GP positioning between two UL SRS resource sets |
Nokia, Nokia Shanghai Bell |
R4-2211226 |
LS on GP positioning between two UL SRS resource sets |
Nokia, Nokia Shanghai Bell |
R4-2211227 |
WF on FeMIMO maintenance |
Samsung |
9.18.1.1 |
Impact of MPE enhancements |
|
R4-2207778 |
On per-beam based PMPR |
Apple |
R4-2208601 |
Discussion on clarification of P-MPR for Rel-17 eMIMO |
vivo |
R4-2208602 |
CR for clarification of P-MPR for Rel-17 eMIMO |
vivo |
R4-2208775 |
Discussion on Impact of MPE enhancements |
ZTE Corporation |
R4-2210002 |
Draft CR on P-MPR reporting and configured transmit power |
Apple AB |
9.18.1.2 |
SRS related impact |
|
R4-2207663 |
Transmissions on a gap between SRSs |
Qualcomm Incorporated |
R4-2207779 |
On SRS switching in FeMIMO |
Apple |
R4-2208381 |
GP position handling in gap between two UL SRS resource sets |
Nokia, Nokia Shanghai Bell |
R4-2208383 |
[Draft] LS on GP positioning between two UL SRS resource sets |
Nokia, Nokia Shanghai Bell |
R4-2209167 |
Remaining issues for SRS |
Huawei, HiSilicon |
9.18.2 |
RRM core requirement maintenance |
|
R4-2210300 |
Email discussion summary for [103-e][228] NR_feMIMO_RRM_1 |
Moderator (Intel) |
R4-2210497 |
Email discussion summary for [103-e][228] NR_feMIMO_RRM_1 |
Moderator (Intel) |
R4-2210616 |
WF on FeMIMO RRM impact for unified TCI |
Intel |
R4-2211148 |
WF on FeMIMO RRM requirements for inter-cell beam management and TRP-specific link recovery |
Huawei |
R4-2211149 |
LS on active TCI state list for UL TCI |
Nokia |
R4-2211203 |
WF on FeMIMO RRM impact for unified TCI |
Intel |
9.18.2.1 |
Unified TCI for DL and UL |
|
R4-2207806 |
Discussion on RRM requirements for Unified TCI |
Apple |
R4-2208058 |
Discussion on remaining issue about Unified TCI state in FeMIMO |
Intel Corporation |
R4-2208279 |
Draft CR to TS38.133 Corrections on R17 unified TCI requirement |
Samsung |
R4-2208465 |
Discussion on unified TCI for DL and UL |
MediaTek Inc. |
R4-2208466 |
CR on known condition of unified TCI for UL |
MediaTek Inc. |
R4-2208776 |
Discussion on Unified TCI for DL and UL |
ZTE Corporation |
R4-2209005 |
Discussion on RRM remaining issues for R17 unified TCI framework |
Huawei, Hisilicon |
R4-2209006 |
DraftCR on maintaining TCI state switching requirements for R17 unified TCI |
Huawei, Hisilicon |
R4-2209500 |
Discussion on remaining issues in RRM requirements for unified TCI in R17 feMIMO |
vivo |
R4-2209501 |
CR on unified TCI in R17 feMIMO |
vivo |
R4-2210052 |
Remaining issues on unified TCI switching delay requirement |
Nokia, Nokia Shanghai Bell |
R4-2210053 |
DraftCR on DCI based DL and UL TCI switching delay requirements |
Nokia, Nokia Shanghai Bell |
R4-2210138 |
RRM requirements of unified TCI state for FeMIMO |
Ericsson |
R4-2210139 |
CR on unified TCI state switching requirements |
Ericsson |
R4-2211144 |
CR on unified TCI in R17 feMIMO |
vivo |
9.18.2.2 |
Inter-cell beam management |
|
R4-2207807 |
Discussion on RRM requirements for inter-cell beam management |
Apple |
R4-2207808 |
CR on maintenance of Inter-cell L1-RSRP measurement requirements |
Apple |
R4-2208059 |
Discussion on remaining issue about inter-cell beam management in FeMIMO |
Intel Corporation |
R4-2208278 |
Draft CR to TS38.133 Corrections on R17 L1-RSRP requirement on NSC |
Samsung |
R4-2208467 |
Discussion on inter cell beam management |
MediaTek Inc. |
R4-2208468 |
CR on measurement restriction and scheduling availability for inter cell L1-RSRP measurement |
MediaTek Inc. |
R4-2209007 |
Discussion on RRM remaining issues for R17 inter-cell beam managements |
Huawei, Hisilicon |
R4-2209008 |
DraftCR on maintaining L1-RSRP measurement requirements for R17 inter-cell beam managements |
Huawei, Hisilicon |
R4-2209134 |
DraftCR on maintaining L1-RSRP measurement requirements for R17 inter-cell beam managements |
Huawei, Hisilicon |
R4-2209502 |
Discussion on remaining issues in RRM requirements for inter-cell L1 beam measurements in R17 feMIMO |
vivo |
R4-2209503 |
CR on L1-RSRP measurement requirements for inter-cell BM in R17 |
vivo |
R4-2209786 |
DraftCR on maintenance of Inter-cell L1-RSRP measurement requirements |
Apple |
R4-2210054 |
Remaining issues on inter-cell beam management |
Nokia, Nokia Shanghai Bell |
R4-2210140 |
RRM requirements for inter-cell BM in FeMIMO |
Ericsson |
R4-2210141 |
CR on L1-RSRP measurements for a cell with different PCI from serving cell |
Ericsson |
R4-2211113 |
Draft CR to TS38.133 Corrections on R17 L1-RSRP requirement on NSC |
Samsung |
R4-2211114 |
CR on L1-RSRP measurement requirements for inter-cell BM in R17 |
vivo |
R4-2211160 |
DraftCR on maintaining L1-RSRP measurement requirements for R17 inter-cell beam managements |
Huawei, Hisilicon |
R4-2211188 |
CR on measurement restriction and scheduling availability for inter cell L1-RSRP measurement |
MediaTek Inc. |
9.18.2.3 |
Others |
|
R4-2207809 |
Discussion on other RRM requirements for FeMIMO |
Apple |
R4-2209009 |
Discussion on remaining issues for R17 TRP specific BFR |
Huawei, Hisilicon |
R4-2209010 |
DraftCR on maintaining R17 TRP specific BFR requirements |
Huawei, Hisilicon |
R4-2209135 |
DraftCR on maintaining R17 TRP specific BFR requirements |
Huawei, Hisilicon |
R4-2209504 |
Discussion on remaining issues in other RRM impacts in R17 feMIMO |
vivo |
R4-2210050 |
DraftCR on maintenance of TRP specific BFD requirements |
Apple |
R4-2210055 |
Remaining issues on other items of Rel-17 feMIMO RRM |
Nokia, Nokia Shanghai Bell |
R4-2210142 |
Discussion on TRP specific link recovery procedures |
Ericsson |
R4-2210143 |
CR on TRP specific CBD and BFR requirements |
Ericsson |
R4-2211115 |
DraftCR on maintaining R17 TRP specific BFR requirements |
Huawei, Hisilicon |
R4-2211116 |
CR on TRP specific CBD and BFR requirements |
Ericsson |
9.18.3 |
RRM performance requirements |
|
R4-2208060 |
Discussion on FeMIMO test case |
Intel Corporation |
R4-2208276 |
Discussion on RRM Performance part for Rel-17 NR FeMIMO |
Samsung |
R4-2208277 |
Draft CR to TS38.133 Accuracy Requirement for R17 L1-SINR Measurement on NSC |
Samsung |
R4-2208510 |
Discussion on test cases for further enhancement on MIMO for NR |
CMCC |
R4-2209011 |
Discussion on RRM test cases for R17 NR FeMIMO |
Huawei, Hisilicon |
R4-2209505 |
Discussion on perf requirements and test cases in R17 feMIMO |
vivo |
R4-2209779 |
Discussion on RRM performance requirements for FeMIMO |
Apple |
R4-2210144 |
Scope of RRM test cases for FeMIMO |
Ericsson |
R4-2210301 |
Email discussion summary for [103-e][229] NR_feMIMO_RRM_2 |
Moderator (Samsung) |
R4-2210498 |
Email discussion summary for [103-e][229] NR_feMIMO_RRM_2 |
Moderator (Samsung) |
R4-2210617 |
WF on FeMIMO RRM performance requirements |
Samsung |
9.18.4 |
UE Demodulation and CSI requirements |
|
R4-2210334 |
Email discussion summary for [103-e][328] NR_FeMIMO_Demod |
Moderator (Samsung) |
R4-2210531 |
Email discussion summary for [103-e][328] NR_FeMIMO_Demod |
Moderator (Samsung) |
R4-2210669 |
WF on CSI requirement for Rel-17 FeMIMO |
Samsung |
R4-2210670 |
WF on demodulation requirement for Enhancement on HST-SFN deployment |
Ericsson |
R4-2210671 |
WF on demodulation requirement for Enhancement on Multi-TRP |
Huawei |
9.18.4.1 |
General |
|
R4-2208265 |
On General for FeMIMO |
Nokia, Nokia Shanghai Bell |
9.18.4.2 |
Demodulation requirements |
|
R4-2208494 |
Views on FeMIMO Demodulation requirements |
Samsung |
9.18.4.2.1 |
Enhancement on HST-SFN scenario |
|
R4-2208477 |
Views on Rel-17 HST-SFN scheme |
NTT DOCOMO, INC. |
R4-2208509 |
Discussion on demodulation requirements for enhancement to support HST-SFN |
CMCC |
R4-2209696 |
Discussion on the PDSCH requirement for HST-SFN scenario |
Ericsson |
R4-2209887 |
Discussion on UE FeMIMO demod HST-SFN |
Huawei, HiSilicon |
R4-2209888 |
Simulation results on UE FeMIMO demod HST-SFN |
Huawei, HiSilicon |
R4-2210151 |
Views on FeMIMO HST Performance Requirements |
Qualcomm Incorporated |
9.18.4.2.2 |
Enhancement on Multi-TRP |
|
R4-2208840 |
Discussion on demodulation performance requirements definition for Rel17 multi-TRP |
MediaTek Inc. |
R4-2209697 |
Discussion on the enhancement on Multi-TRP |
Ericsson |
R4-2209889 |
Discussion on UE FeMIMO demod mTRP |
Huawei, HiSilicon |
R4-2209890 |
Simulation results on UE FeMIMO demod mTRP |
Huawei, HiSilicon |
R4-2210152 |
Views on Performance Requirements for Enhanced Multi-TRP |
Qualcomm Incorporated |
9.18.4.3 |
CSI requirements |
|
R4-2208495 |
Discussion and simulation results for Rel-17 CSI reporting under FeMIMO WI |
Samsung |
9.18.4.3.1 |
CSI reporting for Multi-TRP transmission |
|
R4-2209698 |
Discussion on the CSI reporting for Multi-TRP transmission |
Ericsson |
R4-2209735 |
On CSI reporting for Multi-TRP transmission for FeMIMO |
Nokia, Nokia Shanghai Bell |
R4-2209891 |
Discussion on UE FeMIMO CSI mTRP |
Huawei, HiSilicon |
R4-2210149 |
Views on m-TRP CSI Performance Requirements |
Qualcomm Incorporated |
9.18.4.3.2 |
Rel-17 eType II port selection codebook |
|
R4-2209699 |
Discussion on the Rel-17 eType II port selection codebook |
Ericsson |
R4-2209736 |
On Rel-17 eType II port selection codebook for FeMIMO |
Nokia, Nokia Shanghai Bell |
R4-2209892 |
Discussion on UE FeMIMO CSI FeTypeII PS codebook |
Huawei, HiSilicon |
R4-2210150 |
Views on Performance Requirements for Further Enhanced TypeII Port Selection Codebook |
Qualcomm Incorporated |
9.19.1 |
General |
|
R4-2208474 |
Clarification of supporting bands and open issues in RedCap UE |
Facebook Japan K.K. |
R4-2210268 |
Email discussion summary for [103-e][133] NR_RedCap |
Moderator (Ericsson) |
R4-2210465 |
Email discussion summary for [103-e][133] NR_RedCap |
Moderator (Ericsson) |
9.19.2.1 |
FR1 |
|
R4-2208859 |
Discussion on FDD Tx-Rx carrier centre frequency separation for Redcap UE |
Xiaomi |
9.19.2.1.1 |
Tx requirements (power class) |
|
R4-2209488 |
CR on RedCap FR1 |
Ericsson, Sony |
R4-2210794 |
CR on RedCap FR1 |
Ericsson, Sony |
9.19.2.1.2 |
Rx requirements (REFSENS, etc) |
|
R4-2207712 |
Draft CR on RedCap FR1 RF |
Sony, Ericsson |
R4-2208475 |
Draft CR on TS 38.101-1 Correction on REFSENS requirements for RedCap UE |
Facebook Japan K.K. |
R4-2208684 |
CR to TS38.101-1: Corrections on Redcap requirements |
ZTE Corporation |
R4-2210791 |
Draft CR on RedCap FR1 RF |
Sony, Ericsson |
R4-2210792 |
CR to TS38.101-1: Corrections on Redcap requirements |
ZTE Corporation |
9.19.2.2.1 |
Tx requirements (power class, UE type) |
|
R4-2209357 |
CR for 38.101-2 to correct the errors and add the missing requirements for FR2 RedCap UE |
Huawei, HiSilicon |
R4-2210793 |
CR for 38.101-2 to correct the errors and add the missing requirements for FR2 RedCap UE |
Huawei, HiSilicon |
9.19.2.2.2 |
Rx requirements |
|
R4-2209356 |
Clarification on DL MIMO for FR2 RedCap UE with draft LS |
Huawei, HiSilicon |
R4-2209489 |
CR on RedCap FR2 |
Ericsson, Sony |
R4-2210795 |
CR on RedCap FR2 |
Ericsson, Sony |
R4-2211270 |
CR on RedCap FR1 RF |
Ericsson |
R4-2211271 |
CR on RedCap FR2 |
Ericsson |
9.19.3 |
RRM core requirements |
|
R4-2210286 |
Email discussion summary for [103-e][214] NR_redcap_RRM_1 |
Moderator (Ericsson) |
R4-2210483 |
Email discussion summary for [103-e][214] NR_redcap_RRM_1 |
Moderator (Ericsson) |
R4-2210592 |
WF on RedCap RRM requirements |
Ericsson |
R4-2210593 |
LS on CGI reading with autonomous gaps for RedCap |
Ericsson |
R4-2210594 |
LS on measurement capability for RedCap |
CMCC |
R4-2210595 |
Test case list for RedCap RRM performance part |
Ericsson |
9.19.3.1.1 |
General |
|
R4-2208071 |
Discussion on the remaining RRM issues for 1Rx RedCap UEs |
Intel Corporation |
R4-2208112 |
Discussion on remaining issues for general requirements for Redcap UE |
Xiaomi |
R4-2208266 |
Considerations on remaining issues for general aspects on Redcap |
vivo |
R4-2208365 |
Discussion on general requirements on Redcap UE |
OPPO |
R4-2208390 |
On general requirements for RedCap UE |
CMCC |
R4-2208974 |
Discussion on general RRM requirements impacts for RedCap UE |
Huawei, Hisilicon |
R4-2208975 |
Draft CR on applicability rule of requirements for Redcap UE |
Huawei, Hisilicon |
R4-2209048 |
Draft CR to TS 38.133 on definitions and applicability for RedCap |
Nokia, Nokia Shanghai Bell |
R4-2209446 |
Big CR for RedCap for TS 36.133 |
Ericsson |
R4-2209780 |
General discussion UE capability and scheduling availability |
MediaTek Inc. |
R4-2209902 |
Discussions on general requirements for RedCap |
Ericsson |
R4-2209908 |
Draft CR on RRC_IDLE mode requirements for RedCap for TS 38.133 |
Ericsson |
R4-2209913 |
Big CR for RedCap for TS 38.133 |
Ericsson |
R4-2210218 |
General issues on complexity reduction of RedCap UEs |
Qualcomm Incorporated |
R4-2211037 |
Draft CR to TS 38.133 on definitions and applicability for RedCap |
Nokia, Nokia Shanghai Bell |
R4-2211038 |
Draft CR on RRC_IDLE mode requirements for RedCap for TS 38.133 |
Ericsson |
9.19.3.1.2 |
Mobility requirements |
|
R4-2208072 |
Discussion on mobility requirement for RedCap UE |
Intel Corporation |
R4-2208113 |
Discussion on remaining issues for mobility requirements for Redcap UE |
Xiaomi |
R4-2208268 |
Considerations on remaining issues for mobility requirements for Redcap |
vivo |
R4-2208366 |
Discussion on mobility requirements for RedCap UE |
OPPO |
R4-2208391 |
On mobility requirements for RedCap UE |
CMCC |
R4-2208733 |
Requirements under RRC Connected mode for RedCap UEs |
ZTE Corporation |
R4-2208976 |
Discussion on UE mobility requirements due to UE complexity reduction |
Huawei, Hisilicon |
R4-2208977 |
Draft CR on mobility requirements for Redcap UE |
Huawei, Hisilicon |
R4-2209042 |
Discussion on mobility requirements for RedCap |
Nokia, Nokia Shanghai Bell |
R4-2209043 |
Draft CR to TS 38.133 Corrections on mobility requirements for RedCap |
Nokia, Nokia Shanghai Bell |
R4-2209763 |
Discussion on mobility requirements |
MediaTek inc. |
R4-2209773 |
Discussion on mobility requirement for RedCap |
Apple |
R4-2209903 |
Discussions on RedCap mobility requirements |
Ericsson |
R4-2209909 |
Draft CR on SDT requirements for RedCap for TS 38.133 |
Ericsson |
R4-2210220 |
Mobility requirements for RedCap UEs |
Qualcomm Incorporated |
R4-2211039 |
Draft CR on SDT requirements for RedCap for TS 38.133 |
Ericsson |
R4-2211040 |
Draft CR on mobility requirements for Redcap UE |
Huawei, Hisilicon |
R4-2211041 |
Draft CR to TS 38.133 Corrections on mobility requirements for RedCap |
Nokia, Nokia Shanghai Bell |
9.19.3.1.3 |
Timing requirements |
|
R4-2208073 |
Discussion on the use of SSB for timing requirements of RedCap UE |
Intel Corporation |
R4-2208109 |
Draft CR on timing requirements for RedCap UE |
Xiaomi |
R4-2208114 |
Discussion on remaining issues for timing requirements |
Xiaomi |
R4-2208147 |
Discussion on RRM timing requirements for RedCap devices |
CATT |
R4-2208272 |
Reply LS on RSRP measurement before Msg1 or MsgA retransmission |
vivo |
R4-2208367 |
Discussion on timing requirements on Redcap UE |
OPPO |
R4-2208392 |
On timings requirements for RedCap UE |
CMCC |
R4-2208720 |
Timing requirements for RedCap UEs |
ZTE Corporation |
R4-2208978 |
Discussion on UE timing requirements due to UE complexity reduction |
Huawei, Hisilicon |
R4-2209700 |
On timing requirements for RedCap |
Nokia, Nokia Shanghai Bell |
R4-2209701 |
Draft CR Correction on timing requirements for RedCap UEs |
Nokia, Nokia Shanghai Bell |
R4-2209764 |
UE complexity reduction impact on timing requirements |
MediaTek inc. |
R4-2210175 |
Further analysis of UE transmit timing requirements in RedCap |
Ericsson |
R4-2210176 |
Draft CR on UE transmit timing requirements in RedCap |
Ericsson |
R4-2211042 |
Draft CR on timing requirements for RedCap UE |
Xiaomi |
9.19.3.1.4 |
Signalling characteristics |
|
R4-2208148 |
Discussion on BWP switching for RedCap devices |
CATT |
R4-2208269 |
Considerations on remaining issues for signalling characteristics for Redcap |
vivo |
R4-2208368 |
Discussion on signaling characteristics requirements for RedCap UE |
OPPO |
R4-2208393 |
On Signalling characteristics requirements for RedCap UE |
CMCC |
R4-2208394 |
Draft CR to 38.133 introducing RedCap requirements on active BWP switch delay, active TCI state switching delay and UE specific CBW change |
CMCC |
R4-2208721 |
On Signaling characteristics of RedCap UEs |
ZTE Corporation |
R4-2208979 |
Discussion on signaling characteristics due to UE complexity reduction |
Huawei, Hisilicon |
R4-2209046 |
Draft CR to TS 38.133 Signalling characteristics for RedCap |
Nokia, Nokia Shanghai Bell |
R4-2209047 |
Discussion on signalling characteristics for RedCap |
Nokia, Nokia Shanghai Bell |
R4-2209765 |
Discussion on signaling characteristic in RedCap |
MediaTek inc. |
R4-2209770 |
DraftCR on reduced capability Ues for RLM for RedCap |
MediaTek inc. |
R4-2209774 |
Discussion on signalling characteristics for RedCap |
Apple |
R4-2209904 |
Discussions on RedCap signaling characteristics |
Ericsson |
R4-2210221 |
On signaling characteristics for RedCap UEs |
Qualcomm Incorporated |
R4-2211043 |
Draft CR to 38.133 introducing RedCap requirements on active BWP switch delay, active TCI state switching delay and UE specific CBW change |
CMCC |
R4-2211045 |
DraftCR on reduced capability Ues for RLM for RedCap |
MediaTek inc. |
9.19.3.1.5 |
Measurement procedure |
|
R4-2208115 |
Discussion on remaining issues for measurement procedure for Redcap UE |
Xiaomi |
R4-2208149 |
Discussion on use of NCD-SSB for CONNECTED mode measurements for RedCap devices |
CATT |
R4-2208267 |
Considerations on remaining issues for measurement procedure for Redcap |
vivo |
R4-2208369 |
Discussion on measurement requirements for RedCap UE |
OPPO |
R4-2208395 |
On Measurement procedure for RedCap UE |
CMCC |
R4-2208722 |
Measurement procedure of RedCap UEs |
ZTE Corporation |
R4-2208980 |
Discussion on measurement requirements due to UE complexity reduction |
Huawei, Hisilicon |
R4-2209040 |
Draft CR to TS 38.133 Measurement procedures for RedCap |
Nokia, Nokia Shanghai Bell |
R4-2209041 |
Discussion on measurement procedures for RedCap |
Nokia, Nokia Shanghai Bell |
R4-2209445 |
draftCR on inter-RAT NR measurement for RedCap |
Ericsson |
R4-2209766 |
Measurement procedure for RedCap |
MediaTek inc. |
R4-2209771 |
DraftCR on reduced capability Ues for general measurements and intra-frequency |
MediaTek inc. |
R4-2209772 |
DraftCR on reduced capability Ues for inter-frequency and inter-RAT measurements |
MediaTek inc. |
R4-2209775 |
On remaining issues for measurement procedure for RedCap |
Apple |
R4-2209905 |
Discussions on RedCap measurement procedure |
Ericsson |
R4-2210219 |
Measurement procedures for 1Rx UEs |
Qualcomm Incorporated |
R4-2211046 |
draftCR on inter-RAT NR measurement for RedCap |
Ericsson |
R4-2211047 |
draftCR on inter-RAT NR measurement for RedCap |
Ericsson |
R4-2211048 |
DraftCR on reduced capability Ues for general measurements and intra-frequency |
MediaTek inc. |
R4-2211049 |
DraftCR on reduced capability Ues for inter-frequency and inter-RAT measurements |
MediaTek inc. |
R4-2211215 |
DraftCR on reduced capability Ues for general measurements and intra-frequency |
MediaTek inc. |
R4-2211216 |
DraftCR on reduced capability Ues for inter-frequency and inter-RAT measurements |
MediaTek inc. |
9.19.3.2 |
Extended DRX enhancements |
|
R4-2208116 |
Discussion on remaining issues for RedCap eDRX |
Xiaomi |
R4-2208270 |
Considerations on remaining issues for Redcap eDRX |
vivo |
R4-2208370 |
Discussion on eDRX requirements for RedCap UE |
OPPO |
R4-2208396 |
On Extended DRX cycle for RedCap UE |
CMCC |
R4-2208723 |
On extended DRX enhancements for RedCap |
ZTE Corporation |
R4-2208981 |
Discussion on Extended DRX enhancements for RedCap UE |
Huawei, Hisilicon |
R4-2208982 |
Draft CR on measurement requirements for Redcap UE in inactive mode |
Huawei, Hisilicon |
R4-2209044 |
Discussion on eDRX enhancements for RedCap |
Nokia, Nokia Shanghai Bell |
R4-2209045 |
Draft CR to TS 38.133 Correction on cell reselection requirements for RedCap |
Nokia, Nokia Shanghai Bell |
R4-2209444 |
Discussions on eDRX requirements for RedCap |
Ericsson |
R4-2209767 |
Extended DRX in IDLE mode and INACTIVE mode |
MediaTek inc. |
R4-2209776 |
Discussion on RRM requirement with eDRX for RedCap |
Apple |
R4-2210287 |
Email discussion summary for [103-e][215] NR_redcap_RRM_2 |
Moderator (vivo) |
R4-2210484 |
Email discussion summary for [103-e][215] NR_redcap_RRM_2 |
Moderator (vivo) |
R4-2210596 |
WF on eDRX and RRM measurement relaxations requirements for Redcap UE |
vivo |
R4-2210597 |
Reply LS on RSRP measurement before Msg1 or MsgA retransmission |
vivo |
R4-2210598 |
Reply LS on RRM relaxation for Redcap |
vivo |
R4-2210599 |
Reply LS on introduction of an offset to transmit CD-SSB and NCD-SSB at different times |
Ericsson |
R4-2211051 |
Draft CR on measurement requirements for Redcap UE in inactive mode |
Huawei, Hisilicon |
9.19.3.3 |
RRM measurement relaxations |
|
R4-2208117 |
Discussion on remaining issues for RedCap RRM measurement relaxations |
Xiaomi |
R4-2208271 |
Considerations on remaining issues for Redcap RRM relaxation |
vivo |
R4-2208275 |
draft CR for idle state mobility for Redcap |
vivo |
R4-2208371 |
RRM measurement relaxations for RedCap UE |
OPPO |
R4-2208397 |
On RRM measurement relaxation for RedCap UE |
CMCC |
R4-2208724 |
Discussions on RRM measurement relaxations for RedCap UEs |
ZTE Corporation |
R4-2208983 |
Discussion on RRM measurement relaxations for RedCap UE |
Huawei, Hisilicon |
R4-2209702 |
On RRM measurement relaxation for neighbouring cells |
Nokia, Nokia Shanghai Bell |
R4-2209703 |
Draft CR Corrections to RRM measurement relaxations for RedCap |
Nokia, Nokia Shanghai Bell |
R4-2209768 |
RRM measurements relaxation for stationary criterion |
MediaTek inc. |
R4-2209777 |
On RRM relaxation requirement for RedCap |
Apple |
R4-2209906 |
Discussions on RRM measurement relaxations |
Ericsson |
R4-2210222 |
RRM relaxations enhancements for RedCap UE |
Qualcomm Incorporated |
9.19.3.4 |
Others |
|
R4-2208398 |
Reply LS on introduction of an offset to transmit CD-SSB and NCD-SSB at different times |
CMCC |
R4-2208825 |
Further discussion on NCD-SSB for RedCap UE |
vivo |
R4-2208826 |
Reply LS on operation with and without SSB for RedCap UE |
vivo |
R4-2208827 |
Reply LS on introduction of an offset to transmit CD-SSB and NCD-SSB at different times |
vivo |
R4-2208984 |
Reply LS on introduction of an offset to transmit CD-SSB and NCD-SSB at different times |
Huawei, Hisilicon |
R4-2209704 |
On timing offset between CD-SSB and NCD-SSB for RedCap |
Nokia, Nokia Shanghai Bell |
R4-2209781 |
Discussion on incoming LS from other WGs |
MediaTek Korea Inc. |
R4-2209907 |
Discussions on other RedCap issues |
Ericsson |
R4-2209910 |
Draft CR on uplink spatial relation requirements for RedCap for TS 38.133 |
Ericsson |
R4-2211044 |
Draft CR on uplink spatial relation requirements for RedCap for TS 38.133 |
Ericsson |
9.19.4 |
RRM performance requirements |
|
R4-2209049 |
Discussion on RRM performance for RedCap |
Nokia, Nokia Shanghai Bell |
R4-2209911 |
Workplan to RedCap RRM performance requirements |
Ericsson |
R4-2209912 |
Discussions on RRM performance requirements for RedCap |
Ericsson |
R4-2209915 |
Draft CR on side conditions on RRM requirements applicability for RedCap |
Ericsson |
R4-2211050 |
Workplan to RedCap RRM performance requirements |
Ericsson |
9.19.5 |
UE demodulation and CSI requirements |
|
R4-2210335 |
Email discussion summary for [103-e][329] NR_RedCap_Demod |
Moderator (Ericsson) |
R4-2210532 |
Email discussion summary for [103-e][329] NR_RedCap_Demod |
Moderator (Ericsson) |
R4-2210672 |
WF on RedCap UE demodulation and CQI reporting requirements |
Ericsson |
9.19.5.1 |
General |
|
R4-2209055 |
Summary of simulation results for RedCap |
Ericsson |
R4-2209056 |
Update of work plan for RedCap demodulation performance part |
Ericsson |
R4-2209057 |
draft big CR: Introduction of UE demodulation and CSI reporting requirements for RedCap |
Ericsson |
R4-2209058 |
Open issues on UE demodulation and CSI requirements for RedCap |
Ericsson |
R4-2209705 |
On RedCap general UE demodulation and CSI reporting requirements |
Nokia, Nokia Shanghai Bell |
R4-2210931 |
Update of work plan for RedCap demodulation performance part |
Ericsson |
9.19.5.2.1 |
PDSCH/SDR requirements |
|
R4-2207810 |
On PDSCH Demod Requirements for Reduced Capability Devices in NR |
Apple |
R4-2209059 |
PDSCH demodulation requirements for RedCap |
Ericsson |
R4-2209706 |
Discussion on PDSCH requirements |
Nokia, Nokia Shanghai Bell |
R4-2209707 |
Simulation results for Redcap PDSCH |
Nokia, Nokia Shanghai Bell |
R4-2209797 |
Simulation results and discussion on PDSCH requirements for RedCap |
MediaTek inc. |
R4-2209832 |
Discussion on open issues for RedCap PDSCH and SDR requirements |
Huawei, HiSilicon |
R4-2209833 |
Simulation results for RedCap PDSCH and SDR performance requirements |
Huawei, HiSilicon |
R4-2210146 |
Views on RedCap PDSCH/SDR Requirements |
Qualcomm Incorporated |
9.19.5.2.2 |
PDCCH/PBCH requirements |
|
R4-2207811 |
On PDCCH PBCH Demod Requirements for Reduced Capability Devices in NR |
Apple |
R4-2209060 |
PDCCH/PBCH demodulation requirements for RedCap |
Ericsson |
R4-2209708 |
Discussion on PDCCH/PBCH requirements |
Nokia, Nokia Shanghai Bell |
R4-2209709 |
Simulation results for Redcap PDCCH and PBCH |
Nokia, Nokia Shanghai Bell |
R4-2209798 |
Simulation results and discussion on PDCCH requirements for RedCap |
MediaTek inc. |
R4-2209834 |
Discussion and simulation results for RedCap PDCCH and PBCH performance requirements |
Huawei, HiSilicon |
R4-2210147 |
Views on RedCap PDCCH/PBCH requirements |
Qualcomm Incorporated |
9.19.5.3.1 |
CQI requirements |
|
R4-2207812 |
On CQI Reporting Requirements for Reduced Capability Devices in NR |
Apple |
R4-2209061 |
CQI reporting requirements for RedCap |
Ericsson |
R4-2209799 |
Simulation results and discussion on the CQI requirements for RedCap |
MediaTek inc. |
R4-2209835 |
Discussion and simulation results for RedCap CQI reporting requirements |
Huawei, HiSilicon |
9.19.5.3.2 |
PMI/RI requirements |
|
R4-2207813 |
On PMI Reporting Requirements for Reduced Capability Devices in NR |
Apple |
R4-2209062 |
PMI/RI reporting requirements for RedCap |
Ericsson |
R4-2209710 |
Discussion on RI requirements |
Nokia, Nokia Shanghai Bell |
R4-2209800 |
Simulation results and discussion for the PMI requirements for RedCap |
MediaTek inc. |
R4-2209836 |
Discussion and simulation results for RedCap PMI and RI |
Huawei, HiSilicon |
9.20 |
Positioning enhancements for NR |
|
R4-2210288 |
Email discussion summary for [103-e][216] NR_pos_enh_1 |
Moderator (Ericsson) |
R4-2210485 |
Email discussion summary for [103-e][216] NR_pos_enh_1 |
Moderator (Ericsson) |
R4-2210600 |
WF on NR Positioning Enhancements (Part 1) |
Ericsson |
R4-2210601 |
Further reply LS on condition for PRS measurement outside the MG |
Huawei, Hisilicon |
9.20.1 |
RRM core requirement maintenance |
|
R4-2210289 |
Email discussion summary for [103-e][217] NR_pos_enh_2 |
Moderator (CATT) |
R4-2210486 |
Email discussion summary for [103-e][217] NR_pos_enh_2 |
Moderator (CATT) |
R4-2210602 |
WF on NR Positioning Enhancements (Part 2) |
CATT |
R4-2210603 |
LS on Tx TEG framework |
CATT |
R4-2210604 |
LS on switching time for SRS transmission outside initial UL BWP in RRC_INACTIVE |
Huawei |
9.20.1.1 |
UE Rx/Tx and/or gNB Rx/Tx timing delay mitigation |
|
R4-2208025 |
Open issues in core requirements for NR positioning - Rx/Tx timing error mitigation |
Qualcomm Incorporated |
R4-2208210 |
Discussion on UE Rx/Tx and/or gNB Rx/Tx timing delay mitigation |
CATT |
R4-2208725 |
UE RxTx and gNB RxTx timing delay mitigation |
ZTE Corporation |
R4-2208800 |
Remain issues on timing delay error mitigation |
vivo |
R4-2209219 |
Discussion on timing error mitigation for positioning |
Huawei, Hisilicon |
R4-2209220 |
CR on measurement period requirements with multiple Rx TEGs |
Huawei, Hisilicon |
R4-2210092 |
Remaining issues on Rx/Tx delay mitigation. |
Ericsson |
R4-2211062 |
CR on measurement period requirements with multiple Rx TEGs |
Huawei, Hisilicon |
9.20.1.2 |
Latency reduction of positioning measurement |
|
R4-2208026 |
Open issues in core requirements for NR positioning - latency reduction |
Qualcomm Incorporated |
R4-2208211 |
Discussion on latency reduction of positioning measurement |
CATT |
R4-2208212 |
CR on PRS-RSRP measurement period without gaps |
CATT |
R4-2208213 |
CR on PRS-RSRPP measurement period requirements |
CATT |
R4-2208372 |
Discussion on latency reduction of positioning measurements |
OPPO |
R4-2208527 |
Discussion on gapless based positioning measurement |
CMCC |
R4-2208798 |
Remain issues on latency reduction of positioning measurement |
vivo |
R4-2209221 |
Discussion on PRS measurement outside MG |
Huawei, Hisilicon |
R4-2209222 |
CR on requirements for UE Rx-Tx measurement with reduced latency |
Huawei, Hisilicon |
R4-2209223 |
CR on RSTD measurement period requirements without gaps |
Huawei, Hisilicon |
R4-2210093 |
Remaining issues on latency reduced positioning. |
Ericsson |
R4-2211052 |
CR on PRS-RSRP measurement period without gaps |
CATT |
R4-2211053 |
CR on PRS-RSRPP measurement period requirements |
CATT |
R4-2211054 |
CR on requirements for UE Rx-Tx measurement with reduced latency |
Huawei, Hisilicon |
R4-2211055 |
CR on RSTD measurement period requirements without gaps |
Huawei, Hisilicon |
9.20.1.3 |
Measurement in RRC_INACTIVE state |
|
R4-2208027 |
Open issues in core requirements for NR positioning - measurements in RRC_INACTIVE |
Qualcomm Incorporated |
R4-2208214 |
Discussion on measurement in RRC_INACTIVE state |
CATT |
R4-2208215 |
CR on the PRS and RRM measurement requirements in RRC_INACTIVE state |
CATT |
R4-2208373 |
Discussion on positioning measurements in RRC_INACTIVE state |
OPPO |
R4-2208726 |
Positioning measurements in RRC_INACTIVE state |
ZTE Corporation |
R4-2208799 |
Remain issues on PRS measurement in RRC_INACTIVE state |
vivo |
R4-2208801 |
CR to 38.133 on positioning measurement requirements in RRC_INACTIVE state |
vivo |
R4-2209224 |
Discussion on positioning requirements in RRC_INACTIVE |
Huawei, Hisilicon |
R4-2209225 |
CR on general requirements for PRS measurements in RRC Inactive |
Huawei, Hisilicon |
R4-2209226 |
CR on inter-frequency RRM requirements due to PRS measurement in INACTIVE |
Huawei, Hisilicon |
R4-2210094 |
Remaining issues on RRC_INACTIVE state positioning |
Ericsson |
R4-2210173 |
Correction to PRS measurement requirements in RRC inactive state |
Ericsson |
R4-2211063 |
CR on the PRS and RRM measurement requirements in RRC_INACTIVE state |
CATT |
R4-2211064 |
CR to 38.133 on positioning measurement requirements in RRC_INACTIVE state |
vivo |
R4-2211065 |
Correction to PRS measurement requirements in RRC inactive state |
Ericsson |
9.20.1.4 |
Impact on existing UE positioning and RRM requirements |
|
R4-2209227 |
Discussion on impacts to other RAN4 requirements |
Huawei, Hisilicon |
R4-2209228 |
CR to introduce per-FR MG for PRS measurement |
Huawei, Hisilicon |
R4-2209787 |
Correction to RSTD and UE Rx-Tx measurement period requirement in RRC connected state |
Ericsson Inc. |
R4-2210095 |
Additional path measurement and RRM core requirement |
Ericsson |
9.20.1.6 |
Others |
|
R4-2208216 |
Reply LS on the dropping rule of DL signals/channels for capability 1B and 2 |
CATT |
R4-2208727 |
on PRS measurement outside the measurement gap |
ZTE Corporation |
R4-2209229 |
CR on scheduling restriction for PRS-RSRPP measurement |
Huawei, Hisilicon |
R4-2210096 |
Addtional dropping rule for cap 1b and cap2 UE during gapless PRS measurement |
Ericsson |
R4-2211056 |
Reply LS on the dropping rule of DL signals/channels for capability 1B and 2 |
CATT |
R4-2211057 |
CR on scheduling restriction for PRS-RSRPP measurement |
Huawei, Hisilicon |
9.20.2 |
RRM performance requirements |
|
R4-2208222 |
General discussion on R17 ePOS perf part |
CATT |
9.20.2.1 |
UE Rx/Tx and/or gNB Rx/Tx timing delay mitigation |
|
R4-2208217 |
Discussion on performance requirements for UE Rx/Tx and/or gNB Rx/Tx timing delay mitigation |
CATT |
R4-2208804 |
Discussion on performance requirements for timing delay error mitigation |
vivo |
R4-2209230 |
Discussion on accuracy requirements for TEG |
Huawei, Hisilicon |
R4-2209711 |
Discussion on timing error mitigation for NR positioning |
Nokia, Nokia Shanghai Bell |
R4-2210097 |
UE Rx/Tx timing delay mitigation performance |
Ericsson |
R4-2210098 |
Condition for RSTD and UE Rx-Tx time difference measurement reporting |
Ericsson |
R4-2211168 |
Condition for RSTD and UE Rx-Tx time difference measurement reporting |
Ericsson |
R4-2211207 |
Condition for RSTD and UE Rx-Tx time difference measurement reporting |
Ericsson |
9.20.2.2 |
Latency reduction of positioning measurement |
|
R4-2208028 |
Additional simulation results with reduced number of PRS samples |
Qualcomm Incorporated |
R4-2208218 |
Discussion on performance requirements for latency reduction of positioning measurement |
CATT |
R4-2208526 |
Discussion on test cases for latency reduction of positioning measurement |
CMCC |
R4-2208802 |
Discussion on performance requirements for latency reduction of positioning measurements |
vivo |
R4-2208806 |
Draft CR to 38.133 Introduction of positioning measurement accuracy requirements for reduced number of samples |
vivo |
R4-2208807 |
Draft CR to 38.133 Introduction of test case for PRS measurements without gaps |
vivo |
R4-2208808 |
Further simulation results for PRS measurement with reduced number of samples |
vivo |
R4-2209231 |
Discussion on accuracy and tests for latency reduction |
Huawei, Hisilicon |
R4-2210057 |
Discussion on performance requirement for latency reduction |
Nokia, Nokia Shanghai Bell |
R4-2210099 |
Latency reduction performance requirements |
Ericsson |
R4-2210100 |
Addition of Latency reduction performance requirements |
Ericsson |
9.20.2.3 |
Measurement in RRC_INACTIVE state |
|
R4-2208070 |
Discussion on performance requirements for PRS Measurement in RRC_INACTIVE |
Intel Corporation |
R4-2208219 |
Discussion on the performance requirements for the PRS measurement in RRC_INACTIVE state |
CATT |
R4-2208525 |
Discussion on test cases for positioning measurement in RRC_INACTIVE state |
CMCC |
R4-2208803 |
Discussion on performance requirements for PRS measurement in RRC_INACTIVE |
vivo |
R4-2209232 |
Discussion on accuracy and tests for PRS measurement in RRC_INACTIVE |
Huawei, Hisilicon |
R4-2209712 |
Discussion on measurement in RRC_INACTIVE state |
Nokia, Nokia Shanghai Bell |
R4-2210101 |
RRC inactive state performance requirements |
Ericsson |
R4-2210102 |
Accuracy requirement in RRC inactive state |
Ericsson |
R4-2211066 |
Accuracy requirement in RRC inactive state |
Ericsson |
R4-2211206 |
Accuracy requirement in RRC inactive state |
Ericsson |
9.20.2.4 |
Impact on existing UE positioning and RRM requirements |
|
R4-2209233 |
Discussion on TCs for PRS measurement outside MG |
Huawei, Hisilicon |
R4-2210103 |
Additional path measurement report mapping for existing positioning measurements |
Ericsson |
R4-2210104 |
Additional path measurement report mapping for RSTD, UE Rx-Tx time difference measurement. |
Ericsson |
R4-2211058 |
Additional path measurement report mapping for RSTD, UE Rx-Tx time difference measurement. |
Ericsson |
R4-2211205 |
Additional path measurement report mapping for RSTD, UE Rx-Tx time difference measurement. |
Ericsson |
9.20.2.5 |
Enhancements of A-GNSS positioning |
|
R4-2208220 |
Introduction of BDS B2a and B3I signals inTS 36.171 requirements for support of A-GNSS |
CATT, CAICT, CENC |
R4-2208221 |
Introduction of BDS B2a and B3I signals inTS 38.171 requirements for support of A-GNSS |
CATT, CAICT, CENC |
R4-2211130 |
Introduction of BDS B2a and B3I signals inTS 36.171 requirements for support of A-GNSS |
CATT, CAICT, CENC |
R4-2211131 |
Introduction of BDS B2a and B3I signals inTS 38.171 requirements for support of A-GNSS |
CATT, CAICT, CENC |
9.20.2.6 |
Others |
|
R4-2208029 |
On performance requirements for PRS-RSRPP |
Qualcomm Incorporated |
R4-2208805 |
Discussion on performance requirements for PRS-RSRPP |
vivo |
R4-2209234 |
Discussion on accuracy requirements and TCs for PRS-RSRPP |
Huawei, Hisilicon |
R4-2210056 |
Discussion on accuracy requirements for PRS-RSRPP |
Nokia, Nokia Shanghai Bell |
R4-2210105 |
On performance requirements for DL PRS-RSRPP measurement. |
Ericsson |
R4-2210171 |
Work split on performance requirements for positioning enhancement |
Ericsson |
R4-2210172 |
Big DraftCR Template for Performance Requirements for Positioning Enhancement |
Ericsson |
R4-2211059 |
Big DraftCR Template for Performance Requirements for Positioning Enhancement |
Ericsson |
R4-2211060 |
Work split on performance requirements for positioning enhancement |
Ericsson |
R4-2211061 |
Discussion on accuracy requirements and TCs for PRS-RSRPP |
Huawei, Hisilicon |
9.21 |
Multi-Radio Dual-Connectivity enhancements |
|
R4-2210290 |
Email discussion summary for [103-e][218] LTE_NR_DC_enh2 |
Moderator (Huawei, HiSilicon) |
R4-2210487 |
Email discussion summary for [103-e][218] LTE_NR_DC_enh2 |
Moderator (Huawei, HiSilicon) |
R4-2210605 |
WF on R17 further Multi-RAT Dual-Connectivity enhancements |
Huawei, HiSilicon |
9.21.1 |
RRM core requirement maintenance |
|
R4-2207870 |
Discussion on R2 LS on TCI state indication |
MediaTek (Shenzhen) Inc. |
R4-2208815 |
CR 38.133 corrections on L1/L3 measurement requirements for deactivated SCG |
vivo |
R4-2211077 |
CR 38.133 corrections on L1/L3 measurement requirements for deactivated SCG |
vivo |
R4-2211348 |
CR 38.133 corrections on L1/L3 measurement requirements for deactivated SCG |
vivo |
9.21.1.1 |
Efficient activation/de-activation mechanism for SCells |
|
R4-2207751 |
On efficient activation/de-activation mechanism for SCells |
Apple |
R4-2207868 |
Discussion on efficient activation/de-activation mechanism for SCell |
MediaTek (Shenzhen) Inc. |
R4-2207961 |
Efficient activation and deactivation mechanism for SCells |
Qualcomm Incorporated |
R4-2208286 |
Discussion on effiicient activation/deactivation mechanism for Scells |
Ericsson |
R4-2208374 |
Discussion on efficient activation/de-activation mechanism for Scells |
OPPO |
R4-2208583 |
Final aspects on Efficient activation/de-activation mechanism for Scells |
Nokia, Nokia Shanghai Bell |
R4-2208584 |
CR on Efficient activation/de-activation mechanism for Scells |
Nokia, Nokia Shanghai Bell |
R4-2208967 |
Discussion on efficient activation/de-activation mechanism for Scells |
Huawei, Hisilicon |
R4-2208968 |
Draft CR on A-TRS based SCell activation and deactivated delay requirements with multiple downlink Scell |
Huawei, Hisilicon |
R4-2211067 |
CR on Efficient activation/de-activation mechanism for Scells |
Nokia, Nokia Shanghai Bell |
R4-2211068 |
Draft CR on A-TRS based SCell activation and deactivated delay requirements with multiple downlink Scell |
Huawei, Hisilicon |
9.21.1.2 |
Efficient activation/de-activation mechanism for one SCG |
|
R4-2207752 |
On efficient activation/de-activation mechanism for one SCG |
Apple |
R4-2207753 |
TS38.133 CR on SCG activation/deactivation |
Apple |
R4-2207754 |
TS36.133 CR on SCG activation/deactivation |
Apple |
R4-2207869 |
Discussion on efficient activation/de-activation mechanism for one SCG |
MediaTek (Shenzhen) Inc. |
R4-2207872 |
Maintenance CR for SCG activation on 38.133 R17 |
MediaTek (Shenzhen) Inc. |
R4-2207873 |
Maintenance CR for SCG activation delay on 36.133 R17 |
MediaTek (Shenzhen) Inc. |
R4-2207962 |
Efficient activation and deactivation mechanism for one SCG |
Qualcomm Incorporated |
R4-2208052 |
DraftCR to 38133 for interruptions due to RRM measurements on deactivated SCG |
Intel Corporation |
R4-2208053 |
DraftCR to 36133 for interruptions due to RRM measurements on deactivated SCG |
Intel Corporation |
R4-2208287 |
Discussion on efficient activation/de-activation mechanism for one SCG |
Ericsson |
R4-2208585 |
Final aspects on Efficient activation/de-activation mechanism for one SCG |
Nokia, Nokia Shanghai Bell |
R4-2208586 |
CR on Efficient activation/de-activation mechanism for one SCG (section 8) |
Nokia, Nokia Shanghai Bell |
R4-2208587 |
CR on Efficient activation/de-activation mechanism for one SCG (section 9) |
Nokia, Nokia Shanghai Bell |
R4-2208645 |
CR to maintain SCG activation and deactivation delay requirements in TS 38.133 |
OPPO |
R4-2208814 |
Remain issues on Efficient activation/de-activation mechanism for one SCG |
vivo |
R4-2208969 |
Discussion on efficient activation/de-activation mechanism for one SCG |
Huawei, Hisilicon |
R4-2208970 |
Correction on beam failure detection on deactived PSCell |
Huawei, Hisilicon |
R4-2210179 |
Update to UE transmit requirement under deactivated SCG |
Ericsson |
R4-2211071 |
Maintenance CR for SCG activation on 38.133 R17 |
MediaTek (Shenzhen) Inc. |
R4-2211072 |
Maintenance CR for SCG activation delay on 36.133 R17 |
MediaTek (Shenzhen) Inc. |
R4-2211073 |
DraftCR to 38133 for interruptions due to RRM measurements on deactivated SCG |
Intel Corporation |
R4-2211074 |
DraftCR to 36133 for interruptions due to RRM measurements on deactivated SCG |
Intel Corporation |
R4-2211075 |
CR on Efficient activation/de-activation mechanism for one SCG (section 8) |
Nokia, Nokia Shanghai Bell |
R4-2211076 |
CR to maintain SCG activation and deactivation delay requirements in TS 38.133 |
OPPO |
R4-2211163 |
Update to UE transmit requirement under deactivated SCG |
Ericsson |
R4-2211193 |
TS38.133 CR on SCG activation/deactivation |
Apple |
R4-2211194 |
CR on Efficient activation/de-activation mechanism for one SCG (section 9) |
Nokia, Nokia Shanghai Bell |
9.21.1.3 |
Conditional PSCell change and addition |
|
R4-2208288 |
Discussion on conditional PScell change and addition |
Ericsson |
9.21.1.4 |
Others |
|
R4-2208588 |
TCI state indication with direct SCell activation |
Nokia, Nokia Shanghai Bell |
R4-2208589 |
CR for TCI state indication with direct SCell activation |
Nokia, Nokia Shanghai Bell |
R4-2208971 |
Draft CR on interruptions at A-TRS based SCell activation/deactivation with multiple downlink Scells (38.133) |
Huawei, Hisilicon |
R4-2208972 |
Draft CR on Interruptions at A-TRS based SCell activation/deactivation (36.133) |
Huawei, Hisilicon |
R4-2211069 |
Draft CR on interruptions at A-TRS based SCell activation/deactivation with multiple downlink Scells (38.133) |
Huawei, Hisilicon |
R4-2211070 |
Draft CR on Interruptions at A-TRS based SCell activation/deactivation (36.133) |
Huawei, Hisilicon |
R4-2211195 |
CR for TCI state indication with direct SCell activation |
Nokia, Nokia Shanghai Bell |
9.21.2 |
RRM performance requirements |
|
R4-2208289 |
Disucssion on test case for SCG activation and Scell activation |
Ericsson |
R4-2208816 |
Discussion on RRM performance requirements for Multi-Radio Dual-Connectivity enhancements |
vivo |
R4-2208973 |
Discussion on test cases on R17 Further Multi-RAT Dual-Connectivity enhancements |
Huawei, Hisilicon |
9.22 |
Enhanced IIoT and URLLC support |
|
R4-2210302 |
Email discussion summary for [103-e][230] NR_IIOT_URLLC_enh |
Moderator (Nokia, Nokia Shanghai Bell) |
R4-2210499 |
Email discussion summary for [103-e][230] NR_IIOT_URLLC_enh |
Moderator (Nokia, Nokia Shanghai Bell) |
R4-2210618 |
WF on NR_IIOT_URLLC_enh |
Nokia, Nokia shanghai Bell |
R4-2210619 |
Simulation Results for NR_IIOT_URLLC_enh |
Nokia, Nokia shanghai Bell |
9.22.1.1 |
Propagation delay compensation enhancements |
|
R4-2208820 |
Remaining issues for PDC enhancement |
vivo |
R4-2208821 |
Updated simulation results for TRS based PDC |
vivo |
R4-2208822 |
CR to TS 38.133 Correction to measurements requirements for PDC |
vivo |
R4-2209235 |
On RRM requirements for PDC enhancements |
Huawei, Hisilicon |
R4-2209236 |
CR on requirements for UE Rx-Tx measurement for PDC |
Huawei, Hisilicon |
R4-2209506 |
Discussion of RRM Requirements for Propagation Delay Compensation Enhancements |
Nokia |
R4-2209615 |
CR on correction for RTT-based PDC measurement requirements in 38.133 |
Nokia |
R4-2211117 |
CR to TS 38.133 Correction to measurements requirements for PDC |
vivo |
9.22.1.2 |
Reference point for Te requirements |
|
R4-2208055 |
draftCR to clarify timing reference point for UE UL timing test cases |
Intel Corporation |
R4-2208823 |
Discussion on performance requirements for PDC enhancement |
vivo |
R4-2208824 |
Draft CR to TS 38.133 Introduction of accuracy requirements for PDC |
vivo |
R4-2211159 |
draftCR to clarify timing reference point for UE UL timing test cases |
Intel Corporation |
9.22.2 |
RRM performance requirements |
|
R4-2208651 |
Simulation results for performance part of WI |
Ericsson |
R4-2208652 |
Scope of RRM tests and RMC for TRS |
Ericsson |
R4-2209237 |
Simulation results for TRS based PDC |
Huawei, Hisilicon |
R4-2209238 |
Discussion on accuracy and TCs for PDC |
Huawei, Hisilicon |
R4-2209519 |
Simulation Results for TRS measurement Accuracy |
Nokia |
R4-2209641 |
draftCR on UE Rx-Tx time difference measurement accuracy requirements for RTT-based PDC |
Nokia |
R4-2209642 |
draftCR on test cases for RTT-based PDC UE Rx-Tx time difference measurement requirements |
Nokia |
R4-2210226 |
On performance requirements for RTT-based propagation delay compensation |
Qualcomm Incorporated |
R4-2210434 |
Simulation results for performance part of WI |
Ericsson |
R4-2211118 |
draftCR on UE Rx-Tx time difference measurement accuracy requirements for RTT-based PDC |
Nokia |
9.22.3 |
Demodulation performance and CSI requirements |
|
R4-2209523 |
Sub-slot based PUCCH repetition performance requirements |
Nokia |
R4-2209850 |
Discussion on demodulation and CSI requirements for Rel-17 enhanced IIOT and URLLC support |
Huawei, HiSilicon |
R4-2210336 |
Email discussion summary for [103-e][330] NR_IIOT_URLLC_enh_Demod |
Moderator (Nokia, Nokia Shanghai Bell) |
R4-2210533 |
Email discussion summary for [103-e][330] NR_IIOT_URLLC_enh_Demod |
Moderator (Nokia, Nokia Shanghai Bell) |
R4-2210673 |
WF on enhanced IIoT and URLLC support demodulation and CSI requirements |
Nokia, Nokia Shanghai Bell |
9.23 |
NR Sidelink Relay |
|
R4-2210303 |
Email discussion summary for [103-e][231] NR_SL_relay |
Moderator (OPPO) |
R4-2210500 |
Email discussion summary for [103-e][231] NR_SL_relay |
Moderator (OPPO) |
R4-2210620 |
WF on SL relay test cases |
OPPO |
9.23.1 |
RRM core requirement maintenance |
|
R4-2208375 |
CR to maintain Selection Reselection of relay UE in TS 38.133 |
OPPO |
9.23.2 |
RRM performance requirements |
|
R4-2207741 |
SL relay test scope |
Qualcomm, Inc. |
R4-2208376 |
draft CR on test case for Selection/Reselection of relay UE |
OPPO |
R4-2209012 |
Discussion on RRM test cases for NR SL relay |
Huawei, Hisilicon |
R4-2209013 |
DraftCR on test cases of interruption requirements for NR sidelink relay |
Huawei, Hisilicon |
R4-2211119 |
DraftCR on test cases of interruption requirements for NR sidelink relay |
Huawei, Hisilicon |
R4-2211120 |
draft CR on test case for Selection/Reselection of relay UE |
OPPO |
9.24 |
NR small data transmissions in INACTIVE state |
|
R4-2210304 |
Email discussion summary for [103-e][232] NR_SmallData_INACTIVE |
Moderator (ZTE) |
R4-2210501 |
Email discussion summary for [103-e][232] NR_SmallData_INACTIVE |
Moderator (ZTE) |
R4-2210621 |
LS on the feasibility of testing UE initiated SDT data transmission in RRC_INACTIVE |
Ericsson |
R4-2210622 |
WF on RRM requirements for NR SDT in RRC_INACTIVE mode |
ZTE |
9.24.1 |
RRM core requirement maintenance |
|
R4-2207776 |
On remaining issues for SDT requirement |
Apple |
R4-2208305 |
RSRP measurement reference for TA validation in NR small data transmissions |
LG Electronics Inc. |
R4-2208307 |
CR on TA validation for Rel-17 NR SDT in INACTIVE sate |
LG Electronics Inc. |
R4-2208455 |
Further discussion on RRM requirements for CG-SDT |
Qualcomm Incorporated |
R4-2209028 |
Remaining open issue for NR SDT |
ZTE Wistron Telecom AB |
R4-2209029 |
Draft reply LS to RAN2 on TA validation for CG-SDT |
ZTE Wistron Telecom AB |
R4-2209239 |
Discussion on remaining issues for SDT RRM |
Huawei, Hisilicon |
R4-2209240 |
CR on SDT RRM requirements |
Huawei, Hisilicon |
R4-2209398 |
TA validation window requirements for CG-SDT |
Nokia, Nokia Shanghai Bell |
R4-2209399 |
CR update SDT RRM core requirements |
Nokia, Nokia Shanghai Bell |
R4-2209899 |
Discussions on RRM requirements for Small Data Transmissions |
Ericsson |
R4-2209900 |
Changes to SDT requirements |
Ericsson |
R4-2210111 |
Further discussion on RRM requirements for CG-SDT |
Qualcomm Incorporated |
R4-2210115 |
CR on RRM requirements NR SDT in INACTIVE state for NR-U |
Qualcomm Incorporated |
R4-2210157 |
Discussion on the remaining issues for CG-SDT |
MediaTek Inc. |
R4-2211121 |
CR on TA validation for Rel-17 NR SDT in INACTIVE sate |
LG Electronics Inc. |
R4-2211122 |
reply LS on TA validation for CG-SDT |
ZTE Wistron Telecom AB |
R4-2211123 |
Changes to SDT requirements |
Ericsson |
R4-2211147 |
CR on SDT RRM requirements |
Huawei, Hisilicon |
9.24.2 |
RRM performance requirements |
|
R4-2208456 |
RRM performance requirements for CG-SDT |
Qualcomm Incorporated |
R4-2209030 |
RRM test cases for NR SDT |
ZTE Wistron Telecom AB |
R4-2209241 |
Discussion on TCs for SDT |
Huawei, Hisilicon |
R4-2209400 |
RRM performance requirements for SDT |
Nokia, Nokia Shanghai Bell |
R4-2209901 |
Discussions on RRM performance requirements for SDT |
Ericsson |
R4-2210112 |
RRM performance requirements for CG-SDT |
Qualcomm Incorporated |
10.1 |
LTE inter-band Carrier Aggregation for 2 bands DL with 1 band UL |
|
R4-2210261 |
Email discussion summary [103-e][126] LTE_Baskets |
Moderator (Ericsson) |
10.1.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2208667 |
Revised WID: Rel17 LTE inter-band CA for 2 bands DL with 1 band UL |
Qualcomm Incorporated |
R4-2208668 |
TR 36.717-02-01 v0.8.0 |
Qualcomm Incorporated |
R4-2208669 |
Big CR to TS36.101: Rel-17 LTE inter-band CA for 2 bands DL and 1 band UL CA |
Qualcomm Incorporated |
10.1.3 |
UE RF without specific issues |
|
R4-2208444 |
Draft CR for 36.101 to introduce new configurations for LTE CA with 2 bands DL and 1 band UL |
Samsung, Spark |
R4-2209017 |
Draft CR for 36.101 to add CA_1A-1A-38A_BCS0 |
Huawei, HiSilicon |
R4-2209254 |
Draft CR for 36.101 to add CA_1A-1A-38A_BCS0 |
Huawei, HiSilicon |
R4-2210353 |
Draft CR for 36.101 to introduce new configurations for LTE CA with 2 bands DL and 1 band UL |
Samsung, Spark |
10.2.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2208648 |
Big CR on Introduction of completed R17 3DL 1 UL CA band combinations to TS 36.101 |
Huawei Technologies France |
R4-2208737 |
revised WID Rel-17 LTE inter-band CA for 3 bands DL with 1 band UL |
Huawei Technologies France |
R4-2208758 |
TR 36.717-03-01 LTE inter-band Carrier Aggregation for 3 bands DL with 1 band UL |
Huawei Technologies France |
R4-2209168 |
Draft CR for 36.101 to add CA_1A-3A-3A-7A-38A_BCS0 CA_1A-1A-3A-7A-38A_BCS0 and CA_1A-1A-3C-7A-38A_BCS0 |
Huawei, HiSilicon |
R4-2209169 |
Draft CR for 36.101 to add the band combination CA_3A-3A-7A-38A |
Huawei, HiSilicon |
10.2.3 |
UE RF without specific issues |
|
R4-2208446 |
Draft CR for 36.101 to introduce new configurations for LTE CA with 3 bands DL and 1 band UL |
Samsung, Spark |
R4-2209018 |
Draft CR for 36.101 to add CA_1A-1A-3A-38A_BCS0 and CA_1A-1A-3C-38A_BCS0 |
Huawei, HiSilicon |
R4-2209019 |
Draft CR for 36.101 to add CA_1A-1A-7A-38A_BCS0 |
Huawei, HiSilicon |
R4-2209255 |
Draft CR for 36.101 to add CA_1A-1A-3A-38A_BCS0 and CA_1A-1A-3C-38A_BCS0 |
Huawei, HiSilicon |
R4-2209256 |
Draft CR for 36.101 to add CA_1A-1A-7A-38A_BCS0 |
Huawei, HiSilicon |
10.3.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2209534 |
Revised WID: LTE Advanced inter-band CA Rel-17 for x bands DL (x=4, 5, 6) with 1 band UL |
Nokia, Nokia Shanghai Bell |
R4-2209535 |
TR 36.717-04-01 v0.9.0 |
Nokia, Nokia Shanghai Bell |
R4-2209536 |
Updated scope of TR: LTE inter-band CA for 4/5/6 bands DL with 1 band UL |
Nokia, Nokia Shanghai Bell |
R4-2209785 |
Big CR to TS 36.101: LTE Advanced inter-band CA Rel-17 for x bands DL (x=4, 5, 6) with 1 band UL |
Nokia, Nokia Shanghai Bell |
R4-2210354 |
Updated scope of TR: LTE inter-band CA for 4/5/6 bands DL with 1 band UL |
Nokia, Nokia Shanghai Bell |
10.3.3 |
UE RF with 5 LTE bands CA |
|
R4-2208447 |
Draft CR for 36.101 to introduce new configurations for LTE CA with X bands DL and 1 band UL |
Samsung, Spark |
10.4.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2209173 |
Big CR for TS 36.101: Introduction of completed LTE CA for 2 bands DL with 2 bands UL (Rel-17) |
Huawei, HiSilicon |
R4-2209174 |
Revised WID for LTE inter-band CA for 2 bands DL with 2 bands UL |
Huawei, HiSilicon |
R4-2209250 |
TR 36.717-02-02 v0.5.0 |
Huawei, HiSilicon |
R4-2209814 |
TR 36.717-02-02 v0.6.0 |
Huawei, HiSilicon |
10.4.3 |
UE RF without specific issues |
|
R4-2208445 |
Draft CR for 36.101 to introduce new configurations for LTE CA with 2 bands DL and 2 bands UL |
Samsung, Spark |
R4-2208449 |
TP for TR 36.717-02-02 CA_1-40 |
Samsung, Spark |
R4-2208450 |
TP for TR 36.717-02-02 CA_28-40 |
Samsung, Spark |
R4-2210064 |
draft CR 36101 to add CA_3C-26A |
Ericsson, Telstra |
R4-2210065 |
draft CR 36101 to add CA_7C-26A |
Ericsson, Telstra |
R4-2210355 |
TP for TR 36.717-02-02 CA_1-40 |
Samsung, Spark |
R4-2210356 |
TP for TR 36.717-02-02 CA_28-40 |
Samsung, Spark |
10.5.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2207642 |
TR 36.717-03-02 v0.7.0 TR update for LTE-A inter-band CA for x bands (x=3,4,5) DL with 2 bands UL in Rel-17 |
LG Electronics UK |
R4-2207643 |
Revised WID on LTE-A inter-band CA for x bands (x=3,4,5) DL with 2 bands UL in Rel-17 |
LG Electronics UK |
R4-2207644 |
Introduction of LTE-A inter-band CA for x bands (x=3,4,5) DL with 2 bands UL to TS36.101 |
LG Electronics UK |
10.5.3 |
UE RF without MSD |
|
R4-2208448 |
Draft CR for 36.101 to introduce new configurations for LTE CA with X bands DL and 2 bands UL |
Samsung, Spark |
R4-2210060 |
draft CR 36101 to add CA_1A-3A-7C-26A, CA_1A-3C-7A-26A, CA_1A-3C-7C-26A |
Ericsson, Telstra |
R4-2210061 |
draft CR 36101 to add CA_1A-3C-26A |
Ericsson, Telstra |
R4-2210062 |
draft CR 36101 to add CA_1A-7C-26A |
Ericsson, Telstra |
R4-2210063 |
draft CR 36101 to add CA_3A-7C-26A, CA_3C-7A-26A, CA_3C-7C-26A |
Ericsson, Telstra |
10.6.1 |
RRM Core (36.133) |
|
R4-2209470 |
CR on adding B48 for M1/M2/NB1/NB2 |
Ericsson |
R4-2211274 |
CR on adding B48 for M1/M2/NB1/NB2 |
Ericsson |
10.7.2 |
RF requirements |
|
R4-2209468 |
CR on adding B48 for M1/M2/NB1/NB2 |
Ericsson |
R4-2209469 |
CR on adding B48 for M1/M2/NB1/NB2 |
Ericsson |
R4-2209471 |
CR on adding B48 for M1/M2/NB1/NB2 |
Ericsson |
R4-2209474 |
CR on adding B48 for M1 |
Ericsson |
R4-2209475 |
CR on adding B48 for M1 |
Ericsson |
R4-2209476 |
CR on adding B48 for M1 |
Ericsson |
R4-2209477 |
CR on adding B48 for M1/M2/NB1/NB2 |
Ericsson |
R4-2209478 |
CR on adding B48 for M1/M2/NB1/NB2 |
Ericsson |
R4-2209479 |
CR on adding B48 for M2 |
Ericsson |
R4-2209480 |
CR on adding B48 for M2 |
Ericsson |
R4-2209481 |
CR on adding B48 for M2 |
Ericsson |
R4-2209482 |
CR on adding B48 for M2 |
Ericsson |
R4-2209483 |
CR on adding B48 for NB1/NB2 |
Ericsson |
R4-2209484 |
CR on adding B48 for NB1/NB2 |
Ericsson |
R4-2209485 |
CR on adding B48 for NB1/NB2 |
Ericsson |
R4-2211272 |
CR on adding B48 for M1/M2/NB1/NB2 |
Ericsson |
R4-2211273 |
CR on adding B48 for M1/M2/NB1/NB2 |
Ericsson |
R4-2211275 |
CR on adding B48 for M1/M2/NB1/NB2 |
Ericsson |
R4-2211278 |
CR on adding B48 for M1 |
Ericsson |
R4-2211279 |
CR on adding B48 for M1/M2 |
Ericsson |
R4-2211280 |
CR on adding B48 for M1/M2/NB1/NB2 |
Ericsson |
10.7.3 |
Others |
|
R4-2209472 |
CR on adding B48 for NB1/NB2 |
Ericsson |
R4-2209473 |
CR on adding B48 for NB1/NB2 |
Ericsson |
R4-2211276 |
CR on adding B48 for NB1/NB2 |
Ericsson |
R4-2211277 |
CR on adding B48 for NB1/NB2 |
Ericsson |
10.8 |
Additional enhancements for NB-IoT and LTE-MTC |
|
R4-2208677 |
Discussion and reply LS on UE capability for 16QAM for NB-IoT |
Qualcomm Incorporated |
R4-2209487 |
LS response on UE capability for 16QAM for NB-IoT |
Ericsson |
R4-2209714 |
Discussion on UE capability for 16QAM for NB-IoT |
Nokia, Nokia Shanghai Bell |
10.8.4 |
RRM core requirements maintenance |
|
R4-2208035 |
Open issues in core requirements for NB-IoT neighbor cell measurements in RRC_CONNECTED |
Qualcomm Incorporated |
R4-2208952 |
Discussion on Maintenance for Rel-17 NB-IoT |
Huawei, Hisilicon |
R4-2208953 |
CR on maintenance for NB-IoT R17 |
Huawei, Hisilicon |
R4-2209894 |
Discussions on remaining issues of RRM requirements for NB-IoT |
Ericsson |
R4-2210305 |
Email discussion summary for [103-e][233] NB_IOTenh4_LTE_eMTC6_RRM |
Moderator (Huawei) |
R4-2210502 |
Email discussion summary for [103-e][233] NB_IOTenh4_LTE_eMTC6_RRM |
Moderator (Huawei) |
R4-2210623 |
WF on RRM requirements for Rel-17 NB-IoT and LTE-MTC |
Huawei, HiSilicon |
R4-2211124 |
CR on maintenance for NB-IoT R17 |
Huawei, Hisilicon |
10.8.5 |
RRM performance requirements |
|
R4-2208954 |
Discussion on performance requirements for Rel-17 NB-IoT |
Huawei, Hisilicon |
R4-2208955 |
Draft CR on conditions for NB-IoT connected mode neighbour cell measurement R17 |
Huawei, Hisilicon |
R4-2209895 |
Discussions on performance requirements for NB-IoT |
Ericsson |
10.8.6.1 |
General |
|
R4-2209841 |
Summary of simulation results for Rel-17 NB-IOT and eMTC performance requirements |
Huawei, HiSilicon |
10.8.6.2 |
Demodulation requirements for NB-IoT |
|
R4-2210337 |
Email discussion summary for [103-e][331] NB-IOT_MTC_Demod |
Moderator (Huawei, HiSilicon) |
R4-2210534 |
Email discussion summary for [103-e][331] NB-IOT_MTC_Demod |
Moderator (Huawei, HiSilicon) |
R4-2210674 |
WF on Rel-17 NB-IOT and eMTC performance requirements |
Huawei, HiSilicon |
10.8.6.2.1 |
UE demodulation requirements |
|
R4-2208034 |
On UE performance requirements for 16-QAM NB-IoT |
Qualcomm Incorporated |
R4-2209073 |
UE demodulation requirements for Rel-17 NB-IoT |
Ericsson |
R4-2209837 |
Discussion on NPDSCH performance requirements for Rel-17 NB-IOT |
Huawei, HiSilicon |
R4-2209838 |
Discussion on CQI reporting requirements for Rel-17 NB-IOT |
Huawei, HiSilicon |
10.8.6.2.2 |
BS demodulation requirements |
|
R4-2208081 |
Discussion and simulation results for Rel-17 NB-IoT |
Samsung |
R4-2209074 |
BS demodulation requirements for Rel-17 NB-IoT |
Ericsson |
R4-2209713 |
Discussion on BS demodulation requirements for Additional enhancements for NB-IoT |
Nokia, Nokia Shanghai Bell |
R4-2209839 |
Discussion on NPUSCH format 1 requirements for Rel-17 NB-IOT |
Huawei, HiSilicon |
10.8.6.3 |
Demodulation requirements for MTC |
|
R4-2209075 |
UE demodulation requirements for Rel-17 LTE-MTC |
Ericsson |
R4-2209840 |
Discussion on PDSCH requirements for Rel-17 eMTC |
Huawei, HiSilicon |
11.1 |
Study on enhanced test methods for FR2 in NR |
|
R4-2207691 |
Proposal to conclude the study on enhanced test methods for FR2 in NR |
Apple |
R4-2207692 |
Draft CR to 38.884 on finalizing the study outcomes |
Apple |
R4-2210341 |
Email discussion summary for [103-e][335] FR2_enhTestMethods |
Moderator (Intel Corporation) |
R4-2210538 |
Email discussion summary for [103-e][335] FR2_enhTestMethods |
Moderator (Intel Corporation) |
R4-2210946 |
Draft CR to 38.884 on finalizing the study outcomes |
Apple |
R4-2211332 |
CR to 38.884 on finalizing the study outcomes (Rel-18) |
Apple |
11.1.1 |
Maintenance on objectives 1~6 |
|
R4-2210680 |
WF on OTA test methods for 52.6~71GHz |
Intel Corporation |
11.1.2.1 |
General |
|
R4-2210194 |
General aspects of test methods for 52.6~71GHz |
Intel Corporation |
R4-2210212 |
General aspects of test methods for 52.6~71GHz |
Intel Corporation |
11.1.2.1.3 |
MU assessment |
|
R4-2207927 |
On FR2-2 Measurement Grids |
Keysight Technologies UK Ltd |
11.2 |
Study on Efficient utilization of licensed spectrum that is not aligned with existing NR channel bandwidths |
|
R4-2210269 |
Email discussion summary for [103-e][134] FS_NR_eff_BW_util |
Moderator (Ericsson) |
R4-2210466 |
Email discussion summary for [103-e][134] FS_NR_eff_BW_util |
Moderator (Ericsson) |
R4-2210579 |
WF on carrierBandwidth in SIB1 |
Ericsson |
11.2.1 |
General and TR |
|
R4-2208037 |
TP to TR 38.844: General Updates |
Intel Corporation |
R4-2208040 |
TP for TR 38.868: Conclusions |
Intel Corporation |
R4-2208044 |
TP for TR 38.868: Conclusions |
Intel Corporation |
R4-2209136 |
draft TR 38844 v0.0.8 |
Ericsson |
R4-2210796 |
TP to TR 38.844: General Updates |
Intel Corporation |
11.2.2 |
Evaluation of use of larger channel bandwidths than licensed bandwidth |
|
R4-2208041 |
TP to TR 38.844: General Updates |
Intel Corporation |
R4-2208554 |
TP for wider channel bandwidth |
Huawei, HiSilicon |
R4-2210797 |
TP for wider channel bandwidth |
Huawei, HiSilicon |
11.2.2.1 |
Channel filter assumptions and RB blanking with impacts on UE (ACS, blocking) |
|
R4-2209319 |
Further input on performance when using the next larger channel |
Apple |
R4-2210343 |
Further input on performance when using the next larger channel |
Apple |
R4-2210798 |
Further input on performance when using the next larger channel |
Apple |
11.2.2.2 |
Signaling and configuration (RAN1/RAN2 impacts) aspects |
|
R4-2207707 |
Considerations for wider CBW solutions on Signaling and configuration aspects |
China Telecom Corporation Ltd. |
R4-2208656 |
Signalling and configuration aspects of using larger channel bandwidth |
Nokia, Nokia Shanghai Bell |
R4-2208755 |
TP for 38.844: configuration for the case of larger channel bandwidths than licensed bandwidth |
Ericsson |
R4-2210799 |
Signalling and configuration aspects of using larger channel bandwidth |
Nokia, Nokia Shanghai Bell |
R4-2210801 |
TP for 38.844: configuration for the case of larger channel bandwidths than licensed bandwidth |
Ericsson |
11.2.2.3 |
Other aspects such as detailed solution, complexity, legacy UE, etc |
|
R4-2208657 |
TP to TR 38.844: Legacy UE and RAN4 standard impact to Larger Channel BW than licensed BW |
Nokia, Nokia Shanghai Bell |
R4-2208756 |
TP for 38.844: configuration for the case of larger channel bandwidths than licensed bandwidth for TDD operation |
Ericsson |
R4-2209031 |
Further discussion on the Wider CBW approach |
ZTE Wistron Telecom AB |
R4-2210800 |
TP to TR 38.844: Legacy UE and RAN4 standard impact to Larger Channel BW than licensed BW |
Nokia, Nokia Shanghai Bell |
R4-2210802 |
Further discussion on the Wider CBW approach |
ZTE Wistron Telecom AB |
R4-2210803 |
TP for 38.844: configuration for the case of larger channel bandwidths than licensed bandwidth for TDD operation |
Ericsson |
11.2.3.1 |
Overlapping CBWs from network perspective |
|
R4-2208555 |
TP for Overlapping UE CBWs from Network Perspective |
Huawei, HiSilicon |
R4-2210804 |
TP for Overlapping UE CBWs from Network Perspective |
Huawei, HiSilicon |
11.2.3.2.1 |
Signaling and configuration (RAN1/RAN2 impacts) aspects |
|
R4-2208881 |
TP for 38.844: corrections including the case of combined UE CBW (one cell) |
Ericsson Limited |
R4-2209540 |
TP to TR 38.844: On RAN1 and RAN2 impact for combined UE CBW (one cell) |
Nokia, Nokia Shanghai Bell |
R4-2210805 |
TP to TR 38.844: On RAN1 and RAN2 impact for combined UE CBW (one cell) |
Nokia, Nokia Shanghai Bell |
R4-2210806 |
TP for 38.844: corrections including the case of combined UE CBW (one cell) |
Ericsson Limited |
11.2.3.2.2 |
Other aspects such as detailed solution, complexity, legacy UE, etc |
|
R4-2209541 |
TP to TR 38.844: On UE receiver selectivity requirements for combined UE CBW (one cell) |
Nokia, Nokia Shanghai Bell |
R4-2210807 |
TP to TR 38.844: On UE receiver selectivity requirements for combined UE CBW (one cell) |
Nokia, Nokia Shanghai Bell |
11.2.3.3 |
Overlapping CA (two cells) |
|
R4-2208556 |
TP for overlapping CA |
Huawei, HiSilicon |
R4-2209032 |
Further discussion on the overlapping CA approach |
ZTE Wistron Telecom AB |
R4-2210808 |
TP for overlapping CA |
Huawei, HiSilicon |
R4-2210809 |
Further discussion on the overlapping CA approach |
ZTE Wistron Telecom AB |
11.2.3.4 |
Overall method comparisons |
|
R4-2208038 |
TP to TR 38.844: Method comparisons |
Intel Corporation |
R4-2208042 |
TP to TR 38.844: Method comparisons |
Intel Corporation |
R4-2208557 |
TP for overall method comparisons |
Huawei, HiSilicon |
R4-2208658 |
TP to TR 38.844: Update to summary of wider CBW method |
Nokia, Nokia Shanghai Bell |
R4-2209137 |
TP to TR 38.844: Section 7 Comparison between different schemes |
Ericsson |
12.1 |
Introduction of LTE TDD band in 1670-1675 MHz |
|
R4-2210262 |
Email discussion summary for [103-e][127] R18_LTE_TDD_1.6Hz |
Moderator (Ligado Networks) |
R4-2210459 |
Email discussion summary for [103-e][127] R18_LTE_TDD_1.6Hz |
Moderator (Ligado Networks) |
R4-2210572 |
WF on Introduction of LTE TDD band in 1670 – 1675 MHz |
Ligado Networks |
12.1.1 |
General |
|
R4-2207965 |
Work plan for Introduction of LTE TDD band in 1670 – 1675 MHz |
Ligado Networks |
R4-2207966 |
Emission Requirements for LTE TDD band in 1670 – 1675 MHz |
Ligado Networks |
12.1.2 |
UE RF requirements |
|
R4-2209110 |
n24 emission to 1670 - 1671 MHz |
Nokia |
12.1.3 |
BS RF requirements |
|
R4-2209539 |
BS requirements for LTE TDD band in 1670-1675 MHz |
Nokia, Nokia Shanghai Bell |
13 |
Liaison and output to other groups |
|
R4-2210270 |
Email discussion summary for [103-e][135] NR_reply_LS_UE_RF_Canadan77 |
Moderator (Apple) |
R4-2210306 |
Email discussion summary for [103-e][234] LS_reply |
Moderator (Apple) |
R4-2210467 |
Email discussion summary for [103-e][135] NR_reply_LS_UE_RF_Canadan77 |
Moderator (Apple) |
R4-2210503 |
Email discussion summary for [103-e][234] LS_reply |
Moderator (Apple) |
R4-2210580 |
WF on FR2 requirement applicability over ETC |
Qualcomm |
R4-2210624 |
LS reply on coordination of R17 gap features |
MediaTek |
R4-2210625 |
Reply LS on BWP operation without bandwidth restriction |
Qualcomm |
R4-2210626 |
WF on R17 gap coordination and BWP operation without BW restriction |
Apple |
R4-2211219 |
WF on R17 gap coordination and BWP operation without BW restriction |
Apple |
13.1.1 |
Coordination of R17 gap features (R2-2203879) |
|
R4-2207761 |
On coordination of R17 gap features |
Apple |
R4-2208105 |
Discussion on the coordination of R17 gap features |
Xiaomi |
R4-2208274 |
Discussion on coordination of R17 gap features |
vivo |
R4-2208303 |
Discussion on LS on coordination of R17 gap features |
MediaTek inc. |
R4-2208377 |
Discussion on coordination of R17 gap features |
OPPO |
R4-2209244 |
reply LS on coordination of R17 gap features |
Huawei, Hisilicon |
R4-2209452 |
Reply LS on gap coordination |
Ericsson |
13.2.1 |
BWP operation without bandwidth restriction (R2-2204009) |
|
R4-2207760 |
On BWP operation without bandwidth restriction |
Apple |
R4-2208399 |
Reply LS On BWP operation without bandwidth restriction |
CMCC |
R4-2208736 |
Reply LS on BWP operation without bandwidth restriction |
ZTE Corporation |
R4-2208828 |
Reply LS on BWP operation without bandwidth restriction |
vivo |
R4-2209245 |
reply LS on BWP operation without bandwidth restriction |
Huawei, Hisilicon |
R4-2209253 |
BWP operation without bandwidth restriction |
Qualcomm Incorporated |
R4-2209769 |
Discussion on incoming LS from other WGs |
MediaTek inc. |
R4-2209916 |
Discussion of BWP operation without bandwidth restriction |
Ericsson |
13.2.3 |
FR2 requirement applicability over ETC |
|
R4-2207639 |
On reply to RAN5 on FR2 requirement applicability over ETC |
Qualcomm Incorporated |
R4-2208637 |
Reply LS on FR2 RF requirements applicability under ETC |
vivo |
R4-2208765 |
Draft reply LS on FR2 Extreme temperature conditions clarifications |
Huawei, HiSilicon |
R4-2209259 |
R15 Reply LS on FR2 ETC |
OPPO |
R4-2210813 |
R15 Reply LS on FR2 ETC |
OPPO |
R4-2211125 |
Reply LS on FR2 requirement applicability over ETC |
OPPO |
13.2.4 |
FR2 UE relative power control tolerance requirements |
|
R4-2207640 |
On RAN5 request for change to FR2 UE relative power control tolerance requirements |
Qualcomm Incorporated |
R4-2208764 |
Draft reply LS on FR2 UE relative power control tolerance requirements |
Huawei, HiSilicon |
R4-2210814 |
Reply LS on FR2 UE relative power control tolerance requirements |
Huawei, HiSilicon |
13.2.5 |
Lower humidity limit in normal temperature test environment (R5-221604) |
|
R4-2208487 |
Handling of humidity inconsistency among specifications |
Samsung |
R4-2208488 |
Draft CR to TS 38.101-1 on humidity condition for normal temperature |
Samsung |
R4-2208489 |
Draft CR to TS 38.101-1 on humidity condition for normal temperature |
Samsung |
R4-2208490 |
Draft CR to TS 38.101-1 on humidity condition for normal temperature |
Samsung |
R4-2208491 |
Draft CR to TS 38.101-2 on humidity condition for normal temperature |
Samsung |
R4-2208492 |
Draft CR to TS 38.101-2 on humidity condition for normal temperature |
Samsung |
R4-2208493 |
Draft CR to TS 38.101-2 on humidity condition for normal temperature |
Samsung |
R4-2208766 |
Draft reply LS on lower humidity limit in normal temperature test environment |
Huawei, HiSilicon |
R4-2209631 |
Draft Reply LS on lower humidity limit in normal temperature test environment |
ZTE Corporation |
R4-2210810 |
Draft Reply LS on lower humidity limit in normal temperature test environment |
ZTE Corporation |
13.2.6 |
Additional RF requirements for NS_03U, NS_05U and NS_43U (R5-221613) |
|
R4-2209091 |
Discussion on the LS on Additional RF requirements for NS_03U, NS_05U and NS_43U |
Xiaomi |
R4-2209368 |
Reply LS on Additional RF requirements for NS_03U, NS_05U and NS_43U |
Huawei, HiSilicon |
R4-2209369 |
CR for 38.101-1 to clarify ASE ASEM for NS_03U, NS_05U and NS_43U (R15) |
Huawei, HiSilicon |
R4-2209370 |
CR for 38.101-1 to clarify ASE ASEM for NS_03U, NS_05U and NS_43U(R16) |
Huawei, HiSilicon |
R4-2209371 |
CR for 38.101-1 to clarify ASE ASEM for NS_03U, NS_05U and NS_43U (R17) |
Huawei, HiSilicon |
R4-2210208 |
Applicability of requirements for NS_xxU |
Qualcomm Incorporated |
R4-2210209 |
Applicability of requirements for NS_xxU |
Qualcomm Incorporated |
R4-2210210 |
Applicability of requirements for NS_xxU |
Qualcomm Incorporated |
R4-2210211 |
Reply LS on Additional RF requirements for NS_03U, NS_05U and NS_43U |
Qualcomm Incorporated |
R4-2210811 |
Applicability of requirements for NS_xxU |
Qualcomm Incorporated |
R4-2211129 |
Reply LS on Additional RF requirements for NS_03U, NS_05U and NS_43U |
Qualcomm Incorporated |
13.2.7 |
SCell dropping in FR2 RF UL-CA tests (R5-221617) |
|
R4-2207656 |
Relative power tolerance and RAN5 test solution |
Qualcomm Incorporated |
R4-2207681 |
Reply to RAN5 LS on SCell Dropping in FR2 RF UL-CA tests |
Apple |
R4-2208603 |
Discussion on SCell dropping in FR2 RF UL-CA tests |
vivo |
R4-2208757 |
Draft Reply LS on SCell Dropping in FR2 RF UL-CA tests |
Ericsson |
R4-2208767 |
Draft reply LS on SCell Dropping in FR2 RF UL-CA tests |
Huawei, HiSilicon |
R4-2209419 |
R16 LS reply on SCC dropping |
OPPO |
R4-2210812 |
Reply LS on SCell dropping in FR2 RF UL-CA tests |
Apple |
13.2.8 |
Others |
|
R4-2210204 |
Configured maximum power in the absence of p-maxEUTRA and p-NR-FR1 |
Qualcomm Incorporated |
R4-2210205 |
Configured maximum power in the absence of p-maxEUTRA and p-NR-FR1 |
Qualcomm Incorporated |
R4-2210206 |
Configured maximum power in the absence of p-maxEUTRA and p-NR-FR1 |
Qualcomm Incorporated |
R4-2210207 |
Further Reply LS on configuration of p-MaxEUTRA and p-NR-FR1 |
Qualcomm Incorporated |
R4-2210815 |
Further Reply LS on configuration of p-MaxEUTRA and p-NR-FR1 |
Qualcomm Incorporated |
R4-2211179 |
Configured maximum power in the absence of p-maxEUTRA and p-NR-FR1 |
Qualcomm Incorporated |
14.1 |
Discussions on R18 basket work items |
|
R4-2207904 |
New WID for Rel-18 Dual Connectivity (DC) of 1 LTE band (1DL/1UL) and 1 NR band (1DL/1UL) |
CHTTL |
R4-2208337 |
New WID: High power UE for NR inter-band Carrier Aggregation with 2 bands downlink and x bands uplink (x=1,2) |
China Telecom |
R4-2208338 |
New WID: Downlink interruption for NR and EN-DC band combinations to conduct dynamic Tx Switching in Uplink |
China Telecom |
R4-2208562 |
Rel-18 WID: Dual Connectivity (DC) of 2 bands LTE inter-band CA (2DL/1UL) and 1 NR band (1DL/1UL) |
Huawei, HiSilicon |
R4-2208680 |
Handling of RAN4 band combination basket WIDs in Rel-18 |
ZTE Corporation |
R4-2208905 |
Draft Basket WID on adding channel bandwidth support to existing NR bands |
Ericsson |
R4-2209185 |
New WID on Rel-18 Power Class 2 UE for NR inter-band CA/DC with or without SUL configurations with x (6>=x>2) bands DL and y (y=1, 2) bands UL |
Huawei, HiSilicon, China Unicom |
R4-2209372 |
New WID on Band combinations for SA NR Supplementary uplink (SUL), NSA NR SUL, NSA NR SUL with UL sharing from the UE perspective (ULSUP) |
Huawei, HiSilicon |
R4-2209373 |
New WID on NR inter-band CA for 5 bands DL with x bands UL (x=1, 2) |
Huawei, HiSilicon |
R4-2209374 |
New WID on Rel-18 Dual Connectivity (DC) of x bands (x=1,2) LTE inter-band CA (xDL1UL) and 4 bands NR inter-band CA (4DL1UL) |
Huawei, HiSilicon |
R4-2209486 |
new WID Additional LTE bands for UE category M1_M2 _NB1_NB2 in Rel-18 |
Ericsson |
R4-2209522 |
Release 18 baskets for two band and three band BC with UL configurations including intra-band ULCA |
Skyworks Solutions Inc. |
R4-2209555 |
New Rel-18 WID: NR Intra-band |
Ericsson |
R4-2209556 |
New Rel-18 WID: LTE 3DL and one NR band |
Ericsson |
R4-2209557 |
New Rel-18 WID: NR CA 4DL/xUL |
Ericsson |
R4-2209558 |
New Rel-18 WID: PC2 for EN-DC with x LTE band + y NR TDD band (x= 2, 3, 4, y=1; x=1, 2, y=2) |
Ericsson |
R4-2209559 |
New Rel-18 WID: PC1.5 for NR CA with xDL and 2UL (1FDD+1TDD); (x= 2, 3, 4) |
Ericsson |
R4-2209739 |
New WID: LTE Advanced inter-band CA Rel-18 for x bands DL (x=4, 5, 6) with 1 band UL |
Nokia, Nokia Shanghai Bell |
R4-2209759 |
New WID: Additional NR bands for UL-MIMO in Rel-18 |
Huawei, HiSilicon |
R4-2209760 |
New WID: Rel-18 LTE inter-band CA for 2 bands DL with 2 band UL |
Huawei, HiSilicon |
R4-2209761 |
New WID: Rel-18 simultaneous Rx/Tx band combinations for NR CA/DC, NR SUL and LTE/NR DC |
Huawei, HiSilicon |
R4-2210106 |
New Rel-18 WID on DC of 4 bands LTE inter-band CA (4DL1UL) and 1 NR band (1DL1UL) |
Nokia, Nokia Shanghai Bell |
R4-2210272 |
Email discussion summary for [103-e][137] R18_basket_WI |
Moderator (RAN4 Chair) |
R4-2210469 |
Email discussion summary for [103-e][137] R18_basket_WI |
Moderator (RAN4 Chair) |
14.2 |
Others |
|
R4-2209426 |
High new WID Power UE support for band n100 for Rail Mobile Radio (RMR) in Europe |
Union Inter. Chemins de Fer |
R4-2209428 |
New WID High Power UE support for band n101 for Rail Mobile Radio (RMR) in Europe |
Union Inter. Chemins de Fer |
R4-2209757 |
Revised WID: RF requirements enhancement for NR FR1 (R17) |
Huawei, HiSilicon |
R4-2209758 |
Revised WID: Further RF requirements enhancement for NR and EN-DC in FR1 (R18) |
Huawei, HiSilicon |
15 |
Any other business |
|
R4-2207701 |
New WID on high power UE for NR inter-band CA with 2 bands UL and 2 bands DL with 26dBm on FDD band |
China Unicom |
R4-2207702 |
New WID on high power UE (power class 2) for NR FDD bands |
China Unicom |
R4-2208718 |
Motivation on basket WID on 4Rx and 8Rx bands |
ZTE Corporation |
R4-2208719 |
New WID on 4Rx_8Rx support for NR bands |
ZTE,China Telecom |
R4-2209607 |
New WID for Power Class 1.5 for NR TDD-TDD intra-band combination |
Verizon |
R4-2209616 |
CR to TR 38.862 on cleanup clauses |
ZTE Corporation |
R4-2210720 |
CR to TR 38.862 on cleanup clauses |
ZTE Corporation |